opt out of automatic export of bindings #459
Closed
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
this patch introduces a new feature - "export-bindings" - to grant
downstream more control over when the bindings are generated.
With the feature disabled in Cargo.toml, the bindings are not exported
automatically on every test run. The user can choose when to export by
explicitly enabling the feature with the --features cargo test flag.
For example, in my Cargo.toml:
```toml
[dependencies]
ts-rs = { version = "11", default-features = false, features = [
"serde-compat",
"no-serde-warnings",
] }
```
And at the time I need to export the bindings:
cargo test --features export-bindings -- 'export_bindings_'
This is somewhat related to Aleph-Alpha#62 and Aleph-Alpha#253.
Collaborator
Author
|
Hi @gustavo-shigueo , thank you for the comment. I'll close this then and continue to use my fork until it becomes available. Thank you for the great tool. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
this patch introduces a new feature - "export-bindings" - to grant downstream more control over when the bindings are generated.
With the feature disabled in Cargo.toml, the bindings are not exported automatically on every test run. The user can choose when to export by explicitly enabling the feature with the --features cargo test flag.
For example, in my Cargo.toml:
And at the time I need to export the bindings:
This is somewhat related to #62 and #253.
Checklist