jaredhanson / jaredhanson/oauth2orize
Decision endpoint
Open
- Dominant language
- JavaScript
- Stars
- 3.5k
- Forks
- 472
- PR merge metrics
- No merged PRs in 30d
Description
In the all-grants example, you should surface the decision endpoint into the actual top-level routes, rather than calling res.render from within the oAuth2.js file.
This will make it easier for people to integrate the example into existing Express apps.
Thanks for the hard work here!
Contributor guide
Research direction
Start by reading the all-grants example and its oAuth2.js file, then trace where the example's top-level routes are defined. The work is complete when the decision endpoint is exposed through those routes instead of being rendered from oAuth2.js, while preserving the example's behavior.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- express, javascript, node.js
- Domain
- api, backend
- Issue type
- Refactor
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100