-
Notifications
You must be signed in to change notification settings - Fork 249
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
feat(schema-engine-wasm): stable skeleton + playground #5111
Conversation
…with JS object via tsify. Fix build.sh script
CodSpeed Performance ReportMerging #5111 will not alter performanceComparing Summary
|
WASM Query Engine file Size
|
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.
TODO: delete once somebody reviews this PR.
|
||
console.log('[adapter]', adapter) | ||
|
||
// TODO: use `engine`. |
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.
Note: TODOs in the TypeScript files changed/introduced by this PR are supposed to be tackled in later PRs.
For now, they act as informative comments only.
# Note: this script started as a copy of the `query-engine-wasm`'s `build.sh` script, but will likely diverge over time. | ||
# For this reason, we're avoiding premature refactoring and keeping the two scripts separate. |
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.
Callout ^
#[derive(Deserialize, Tsify)] | ||
#[tsify(from_wasm_abi)] | ||
pub struct SchemaEngineParams { | ||
// TODO: support multiple datamodels | ||
datamodel: String, | ||
} |
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.
Without tsify::Tsify
, this Rust struct would be converted into a (useless) class instance with related class checks.
It's much more ergonomic to pass un-named JS objects as the SchemaEngine
's constructor input arguments instead.
This PR: