Add signer constructors #5757
Merged
Add signer constructors #5757
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
🦋 Changeset detectedLatest commit: c9b8b7a The changes in this PR will be included in the next version bump. This PR includes changesets to release 1 package
Not sure what this means? Click here to learn what changesets are. Click here if you're a maintainer who wants to add another changeset to this PR |
ernestognw
reviewed
Jun 20, 2025
Amxx
changed the title
Amxx
commented
Jun 20, 2025
Amxx
commented
Jun 20, 2025
Amxx
commented
Jun 20, 2025
Collaborator
Author
|
Note: the changeset is just for RC-1. Will not be part of the final release. |
ernestognw
approved these changes
Jun 20, 2025
Amxx
added a commit
that referenced
this pull request
Jun 20, 2025
Co-authored-by: ernestognw <[email protected]> Signed-off-by: Hadrien Croubois <[email protected]>
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.
When the signer were part of the community repository, we did not have an upgradeable version. It made sens to not have a constructor, because we wanted to be able to use them in an "initializable" manner, without a key set at construction. This was still not upgrade-friendly because of the lack of namespaced storage.
This PR proposes to align the signers with the normal practice in the library:
_setSigner(). This will force that the signer is set at construction, no longer possible to "forget calling it". This is fine for "one time deployment" (non upgradeable, non proxy) accounts.checklist
npx changeset add)