Implement upstream spec changes for component text syntax#2562
Merged
fitzgen merged 2 commits intoJul 10, 2026
Conversation
This commit is an implementation of WebAssembly/component-model#655 where parsing of components is updated in a few locations. This is a breaking change to the text format so it's done in a manner where both the previous and new form are accepted. The plan is to have a release or two of accepting the old syntax and new, then have a release or two of defaulting to only accepting the new syntax, followed by eventually removing support for the old syntax.
fitzgen
approved these changes
Jul 10, 2026
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 commit is an implementation of WebAssembly/component-model#655 where parsing of components is updated in a few locations. This is a breaking change to the text format so it's done in a manner where both the previous and new form are accepted. The plan is to have a release or two of accepting the old syntax and new, then have a release or two of defaulting to only accepting the new syntax, followed by eventually removing support for the old syntax.