Cleanup auth-api Spec
- Dominant language
- JavaScript
- Stars
- 23
- Forks
- 62
- Avg merge
- 24m
- Merged PRs (30d)
- 1
Description
## What is the problem?
* Auth-API spec doesn't follow the standard which we follow and was created long back and didn't make the subsequent updates.
## What is the impact?
* Spec not up-to-date and confuses partners
## Proposed solution
* Cleanup and update the API Spec with endpoints which are needed for the partner, API users and other BC registry applications.
Contributor guide
No contributing guide indexed for this repository
Research direction
The issue names no file, test, or entry point. Start by locating the auth-api specification and the project's standard for API specs, then identify the endpoints required by partners, API users, and BC Registry applications. Done means the specification follows that standard and is current for those users.
Written by the indexing model from the issue text.
Assessment
- Domain
- api, documentation
- Issue type
- Documentation
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100