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

feat: hide nearcore crates behind testing feature #870

Merged
merged 2 commits into from
Jul 22, 2022

Conversation

itegulov
Copy link
Contributor

It seems like it is not possible to configure default features per arch, so I had to do cover everything testing-related with #[cfg(all(not(target_arch = "wasm32"), feature = "testing"))]. LMK if there is a better way.

Relates to near/cargo-near#8

Copy link
Contributor

@austinabell austinabell left a comment

Choose a reason for hiding this comment

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

All lgtm, I don't think there is a better way to do this. I wonder though, would unit-testing be a more clear feature name? Maybe confusing with workspaces? cc @ChaoticTempest

@ChaoticTempest
Copy link
Member

if only they allowed cfg(test) to be usable as a library flag as well, but I guess that's what dev-dependencies are for. And yeah, feel like unit-test or unit-testing would be better as testing is more general and likely confusing with workspaces

@itegulov
Copy link
Contributor Author

Renamed to unit-testing

@itegulov itegulov merged commit 83df045 into master Jul 22, 2022
@itegulov itegulov deleted the daniyar/testing-feature branch July 22, 2022 03:47
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.

3 participants