Skip to content

why-component-model section: Include both file and wasm-tools output#285

Merged
vados-cosmonic merged 1 commit intobytecodealliance:mainfrom
catamorphism:why-component-model-followup
Jul 22, 2025
Merged

why-component-model section: Include both file and wasm-tools output#285
vados-cosmonic merged 1 commit intobytecodealliance:mainfrom
catamorphism:why-component-model-followup

Conversation

@catamorphism
Copy link
Contributor

This is following up on one of @vados-cosmonic's suggestions on #281 .

Copy link
Collaborator

@vados-cosmonic vados-cosmonic left a comment

Choose a reason for hiding this comment

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

Thanks @catamorphism !

A nit that doesn't matter but I'd appreciate some spacing in the markdown in between paragraphs/code blocks/sections. I find markdown hard to parse if everything is just bunched up together.

@vados-cosmonic vados-cosmonic merged commit ff67f45 into bytecodealliance:main Jul 22, 2025
8 checks passed
catamorphism added a commit to catamorphism/component-docs that referenced this pull request Aug 12, 2025
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.

2 participants