Skip to content

Apply backend bindings for watch#369

Open
tjpalmer wants to merge 1 commit intomainfrom
watch-bindings
Open

Apply backend bindings for watch#369
tjpalmer wants to merge 1 commit intomainfrom
watch-bindings

Conversation

@tjpalmer
Copy link
Contributor

@tjpalmer tjpalmer commented Mar 6, 2026

  • Tested with an external backend, where this was failing previously:
Watch starting build #0 at 2026-03-06T19:01:44.840Z
Finished build #0 in 3.588s
Watch starting build #1 at 2026-03-06T19:02:07.253Z
Finished build #1 in 329.622ms
Watch starting build #2 at 2026-03-06T19:02:36.885Z
Finished build #2 in 223.697ms

Signed-off-by: Tom <tom@temper.systems>
@@ -131,6 +124,19 @@ fun prepareBuild(
)
}
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I also looked into making Watcher call prepareBuild, but there's a larger gap for that change. The down side here is if people add other things in the middle of prepareBuild, but I think this is ok for now, anyway.

module.addEnvironmentBindings(lookupFactory(backendId)!!.environmentBindings)
}
},
)
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I could make a superficial test of just this function, but testing for temper watch generally is awkward because of how much infrastructure is currently pulled in there.

@tjpalmer tjpalmer marked this pull request as ready for review March 6, 2026 22:51
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant