oasisprotocol / oasisprotocol/explorer
Can we reduce the number of concepts for hidden scopes
Open
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 13
- Forks
- 13
- Avg merge
- 58m
- Merged PRs (30d)
- 2
Description
- ENABLED_LAYERS_FOR_NETWORK
- wantedScope (not collapsed in search)
- isLayerHidden (not searchable, but is discoverable)
- fixedLayer (pinned, single enabled layer) (see discussions in https://github.com/oasisprotocol/explorer/pull/1242 and https://github.com/oasisprotocol/explorer/pull/1269 )
- scopeFreedom
(previously also: scope.valid https://github.com/oasisprotocol/explorer/pull/1159, getEnabledRuntimesForNetwork + getEnabledLayersForNetwork f5f510e36c3bd6f35957fcaa954cd17a4d0d2613 )
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 with the discussions in pull requests 1242 and 1269, then review the listed concepts and the earlier references to understand how hidden scopes are currently represented. Done requires an agreed, simpler scope model and a clear inventory of which existing concepts and usages must be consolidated.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- blockchain, frontend
- Issue type
- Refactor
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100