Skip to content

Add Wasm CI#164

Open
czechboy0 wants to merge 2 commits intomainfrom
hd-wasm-ci
Open

Add Wasm CI#164
czechboy0 wants to merge 2 commits intomainfrom
hd-wasm-ci

Conversation

@czechboy0
Copy link
Copy Markdown
Contributor

Motivation

Allow generated code from OpenAPI to be used with Wasm.

Modifications

Added CI to discover the current status.

Result

Wasm CI, ensuring we don’t regress Wasm support once it works.

Test Plan

Using this to see the current status.

@czechboy0 czechboy0 added the semver/none No version bump required. label Dec 18, 2025 — with GitHub Codespaces
@diederich
Copy link
Copy Markdown

Worth bumping this to see where we are?

I have this commit lying around which might help?

@diederich
Copy link
Copy Markdown

Thanks for bumping! 🙏 Looks like the error I was seeing. Add the patch to this PR?

@MaxDesiatov
Copy link
Copy Markdown
Member

There are neither socket nor HTTP APIs available in WASI 0.1, besides the current OpenAPI infrastructure available on main isn't compatible with Embedded Swift. At least in the short term, compatibility with Embedded Swift and Web APIs available via JS interop in Swift for Wasm in the browser is a requirement, which this PR doesn't provide, so it's likely to be superseded by #187.

@diederich
Copy link
Copy Markdown

Gotcha - makes sense. We did hack together a fetch based transport and got that to work. I think having build right now could allow that going forward?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

semver/none No version bump required.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants