Skip to content

fix: logic for stubbing outgoing http and fetch-event #268

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Conversation

vados-cosmonic
Copy link
Contributor

This commit fixes one bug and refactors the code to be more granular in the case of differing feature sets.

The reality is more nuanced -- as we must stub wasi:http/types differently depending on whether fetch-event is separately enabled.

Resolves #265

@vados-cosmonic vados-cosmonic force-pushed the fix=remove-http-independent-of-fetch-event branch 2 times, most recently from a8f3b9b to b314f06 Compare July 22, 2025 07:03
Copy link
Member

@tschneidereit tschneidereit left a comment

Choose a reason for hiding this comment

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

Feel free to land this as-is, but I'd much like a follow-up PR with the "remove fetch" change I suggested inline.

vados-cosmonic and others added 2 commits July 23, 2025 08:25
This commit fixes one bug and refactors the code to be more granular
in the case of differing feature sets.

The reality is more nuanced -- as we must stub wasi:http/types
differently depending on whether fetch-event is separately enabled.
Co-authored-by: Till Schneidereit <till@tillschneidereit.net>
@vados-cosmonic vados-cosmonic force-pushed the fix=remove-http-independent-of-fetch-event branch from 540876d to 44c13ef Compare July 22, 2025 23:26
@vados-cosmonic vados-cosmonic merged commit 4bf2d7e into bytecodealliance:main Jul 22, 2025
16 checks passed
@vados-cosmonic vados-cosmonic deleted the fix=remove-http-independent-of-fetch-event branch July 22, 2025 23:44
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.

import of wasi:http@0.2.3 is not disabled with 0.18.3
2 participants