Revise Panes available by Role
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 146
- Forks
- 21
- PR merge metrics
- No merged PRs in 30d
Description
The icons/panes a user can see have several problems. Foremost is that users do not have an under-the-hood pane unless they are a developer (in other words, they can't delete anything). Another issue is that since the spec doesn't mandate a preferences file, we should provide a default logged-in state. I don't understand why we present a sharing icon to the non-logged-in user. There are other inconsistencies. Here is my proposal. I would also be okay with simply logged in and logged out with logged in being all panes available.
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 by reviewing the existing pane and icon visibility rules for developer, logged-in, and logged-out users, then compare them with the proposal and attached image. Identify how the default logged-in state is determined. Done means the role and authentication states expose a consistent, agreed set of panes and icons, including the under-the-hood and sharing controls.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- frontend
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100