-
Notifications
You must be signed in to change notification settings - Fork 20
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
Allow cw-orch wasm compilation without features #342
Allow cw-orch wasm compilation without features #342
Conversation
Deploying with Cloudflare Pages
|
Codecov ReportAttention: Patch coverage is
Additional details and impacted files
|
#[cfg(feature = "daemon")] | ||
pub mod daemon; | ||
|
||
#[cfg(not(target_arch = "wasm32"))] | ||
mod error; | ||
#[cfg(feature = "osmosis-test-tube")] | ||
pub mod osmosis_test_tube; |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We should either arch-flag all the exports or only the non-featured ones (if we assume a user doesn't enable the feature in their wasm env).
Right now daemon is arch-flagged but test-tube is not.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think arch-flagging features would work as well!
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Oups, that's a mistake yes
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
flaggin features doesn't seem to work : rust-lang/cargo#1197
This PR aims to allow adding derive attributes for wasm targets, by not generating any code.
Interface can be removed as well.
Users can also use the
#[cfg(not(target_arch = "wasm32"))]
to shield the interface instead of the interface feature