paritytech / paritytech/host-rust-core
RFC: getPrimaryDotNsName
Nobody has claimed this yet.
- Dominant language
- Swift
- Stars
- 10
- Forks
- 3
- Avg merge
- 1d 10h
- Merged PRs (30d)
- 148
Description
Raised in: #222 · @filvecchiato
Description
getPrimaryDotNsName returns the product's primary dotNS node — a path into the namespace — and the account that controls it, as a (DotNsNode, AccountId) pair.
Motivation
A product can read its own identifier from getProductContext and the user's primary username from getUserId, but nothing tells it which dotNS node it is published under or which account controls that node.
Requirements
- Returns a
(DotNsNode, AccountId)pair. - The
DotNsNodeis a path into the namespace, not a bare label. - The controlling account should generally be signable via
signWithAccount.
Tasks
- RFC document body
- Implementation — rust-core
- Implementation — hosts
- dotli
- Desktop
- iOS
- Android
- host-cli
Note: no RFC drafted yet.
Contributor guide
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 with the context in issue #222 and the requirements here, then define the RFC document body before examining the rust-core and host implementation tasks. Completion requires the RFC plus implementations across dotli, Desktop, iOS, Android, and host-cli, with the stated pair and account-signing expectations addressed.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- android, ios, rust, swift
- Domain
- api, cli, desktop, documentation, mobile
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 30/100