Adding authorization requirements to metadata
Open
Nobody has claimed this yet.
future
- Dominant language
- Makefile
- Stars
- 78
- Forks
- 18
- PR merge metrics
- No merged PRs in 30d
Description
Should we add an authorization object to the transmitter metadata to describe things like token type, scopes, etc that are required?
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
No file, test, or entry point is named. Start by reviewing the transmitter metadata definition and the requirements for token types and scopes; determine whether an authorization object is needed and what it must contain. Done requires an agreed specification or decision recorded for the metadata.
Written by the indexing model from the issue text.
Assessment
- Domain
- authorization
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100