Propagate wasm runfiles - #4168
Merged
Merged
Conversation
UebelAndre
marked this pull request as ready for review
July 26, 2026 15:12
slackito
approved these changes
Jul 27, 2026
slackito
left a comment
slackito
left a comment
Collaborator
There was a problem hiding this comment.
Do we need a test for this?
Collaborator
Author
Yeah, this was actually part of a larger change which I did have testing for but don't feel confident about the design so didn't include it. |
Collaborator
Author
|
#4172 is the larger change I was working on. I would love some ideas there. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This change allows the wasm targets to propagate runfiles with the bindgen outputs.