Alpha -> beta (pad SQ IDs) #1386
Merged
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
Add dual version SubQuery support. v19+ SQ instance will pad block ID values so ordering by created block is such that the lexical order is equivalent to numerical order. Also created_at column has been removed as the padding makes it redundant (it was the time of sync, not the time on chain).
BREAKING CHANGE: 🧨 SDK no longer supports chain 6.x - Drops support for `6.3` spec version - type of `signers` has been changed to `Account` type in `MultiSigDetails` and `MultiSigSigners`. This affects `details` method in `MultiSig` entity and `getMultiSigSigners` in `Identity` entity - Deprecated `getSubsidy` method of the `Account` entity has been removed. - Deprecated `ticker` field has been removed from the interface `MetadataKeyId`. This affects `getCollectionKeys` method from `NftCollection` entity - Deprecated `ticker` field has been removed from `HumanReadable` interfaces for these entities: `Checkpoint`, `CheckpointSchedule`, `CorporateAction`, `DividendDistribution`, `CustomPermissionGroup`, `KnownPermissionGroup`, `MetadataEntry`, `Offering`, - `Ticker` value has been removed from `ScopeType` enum - `ticker` field has been renamed to `assetId` in `ClaimScope` interface - Deprecated `did` and `ticker` fields of the `BaseAsset` entity have been removed. - Deprecated `joinCreator` method of `MultiSig` entity has been removed
BREAKING CHANGE: 🧨 Return type of `MultiSig.getHistoricalProposals` is now changed to `ResultSet<HistoricalMultiSigProposal>` to provide more info about the proposal. This will allow get know information about prunded proposals as well
Contributor
|
🎉 This PR is included in version 27.0.0-alpha.11 🎉 The release is available on: Your semantic-release bot 📦🚀 |
if a user inputs permissions directly on chain there is no validation of their cases. This updates it so incorrect cased permissions are ignored ✅ Closes: DA-1397
VictorVicente
previously approved these changes
Dec 2, 2024
Contributor
|
🎉 This PR is included in version 27.0.0-alpha.12 🎉 The release is available on: Your semantic-release bot 📦🚀 |
|
VictorVicente
approved these changes
Dec 2, 2024
Contributor
Author
|
/fast-forward |
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.
Description
Test run: PolymeshAssociation/middleware-tests#45
Breaking Changes
JIRA Link
Checklist