Skip to content
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

Add support for -J option group #748

Merged
merged 8 commits into from
Sep 10, 2024

Conversation

saulecabrera
Copy link
Member

This commit adds support for the -J option group and enables javy-json and override-json-parse-and-stringify by default.

Additionally, this change improves how the javy cli integration tests are defined by introducing a javy_cli_test which:

  • Produces a test per supported command (compile and build)
  • Provides a set of defaults depending on the command under test

Generating a test per command improves the developer experience of determining failures on particular command configurations.

Lastly, this change bumps the provider to v3, given that new funcionality is introduced as part of enabling javy-json and override-json-parse-and-stringify. In order to test that the compile command remains "frozen", using version 2 of the provider, this commit introduces a static copy of the v2 provided downloaded from the releases section.

  • I've updated the relevant CHANGELOG files if necessary. Changes to javy-cli and javy-core do not require updating CHANGELOG files.
  • I've updated the relevant crate versions if necessary. Versioning policy for library crates
  • I've updated documentation including crate documentation if necessary.

This commit adds support for the `-J` option group and enables
`javy-json` and `override-json-parse-and-stringify` by default.

Additionally, this change improves how the javy cli integration tests
are defined by introducing a `javy_cli_test` which:

* Produces a test per supported command (`compile` and `build`)
* Provides a set of defaults depending on the command under test

Generating a test per command improves the developer experience of
determining failures on particular command configurations.

Lastly, this change bumps the provider to v3, given that new
funcionality is introduced as part of enabling `javy-json` and
`override-json-parse-and-stringify`. In order to test that the `compile`
command remains "frozen", using version 2 of the provider, this commit
introduces a static copy of the v2 provided downloaded from the releases
section.
@saulecabrera
Copy link
Member Author

The failures in CI are caused by rust-lang/rust#123748; in CI, we're using the latest stable, which got updated today. I can repro those failures locally by updating the toolchain.

Copy link
Collaborator

@surma surma left a comment

Choose a reason for hiding this comment

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

Only nits! LGTM.

crates/cli/src/commands.rs Outdated Show resolved Hide resolved
crates/runner/src/lib.rs Show resolved Hide resolved
@saulecabrera saulecabrera merged commit e55fd90 into bytecodealliance:main Sep 10, 2024
7 checks passed
@saulecabrera saulecabrera deleted the handle-more-js-opts branch September 10, 2024 14:15
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