Joystream / Joystream/substrate-versioned-store-module
Versioned internal references
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 1
- Forks
- 4
- PR merge metrics
- No merged PRs in 30d
Description
Currently, it is not possible to require that reference to some entity in a class has to support some specific schema versions. It makes sense to allow expressing this more harsh constraint, and it will be a requirement when wanting to introduce certain new types of schema upgrades.
A simple way could be to change Internal(ClassId) to Internal(ClassId, Option<VersionConstraint>) in PropertyType, where VersionConstraint can be something like
enum VersionConstraint {
Exactly(u16),
AtLeast(u16)
}
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by locating PropertyType and the Internal(ClassId) representation, then inspect how internal references are validated and how schema versions are handled. Define and implement the version-constraint behavior for Exactly and AtLeast, updating all affected reference construction and validation paths; done means references can enforce the requested schema versions.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- blockchain
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100