itowlson
itowlson
@calebschoepp This feels like something that could slot nicely in if/when you are separating "artifact" paths from "source code" paths - you could split the source code watches down further...
_reads 3 emails further on and discovers that @calebschoepp has already done that refactor_ well maybe next time
Just noting that the single-component entry point into build now exists courtesy of the Spin Doctor.
We still want to do it but my refactor definitely introduced exciting new challenges to doing so - see the discussion on https://github.com/fermyon/spin/pull/2478. I would leave it open because it...
Thanks for looking at this @garikAsplund - I've bounced off it a couple of times myself but had forgotten to remove the "good first issue" tag... Unfortunately, I am sceptical...
I don't have anything even close to working I'm afraid. Manifest file changes must trigger a full rebuild and restart, _and_ must reload the watch configuration (because we may now...
It should work... if it's not then that's a bug.
I think you're right. It's not firing for me either. That's a bug: I'll take a look. Thanks!
Thanks for this! I do think this could be a fruitful avenue and I appreciate you coming up with it and exploring it. However, I have a couple of comments,...
Yes, multiple changes _within_ the debounce period get accumulated within watchexec, so trigger a single update. The race condition happens when you have changes that happen _outside_ the debounce period...