Joystream / Joystream/joystream
Remove unique handle constraint enforcement from runtime
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 1.4k
- Forks
- 116
- PR merge metrics
- No merged PRs in 30d
Description
This is a pure metadata issue, so the query node should hande it, not the runtime. We may have similar issues in the content directory, if so, same applies there. Reasonable query node policy is to reject handle updates that do not respect uniqueness, and also ignore initial names which are not unique, leaving them blank. This latter point may impact the query node.
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 the runtime and query-node handling for unique handles, then check whether equivalent enforcement exists in the content directory. The work is done when runtime enforcement is removed and the query node rejects non-unique handle updates while leaving non-unique initial names blank.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- blockchain
- Issue type
- Refactor
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100