Wee tidy to subxt-signer flags #1200
Merged
Conversation
This file contains 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
niklasad1
approved these changes
Oct 9, 2023
|
Aah, I see why subxt-signer sets the subxt features now, so maybe this makes no sense either. Edit: re-added those features but kept the compile_error tweak, so this is super minor now :) |
lexnv
approved these changes
Oct 9, 2023
sergejparity
approved these changes
Oct 9, 2023
tadeohepperle
approved these changes
Oct 9, 2023
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Subxt-signer probably shouldn't bother trying to set the corresponding subxt feature flags when it's enabled; just expect them to be set for each crate independently. And compile_error regardless of whether subxt is enabled