Improve usage under configs with no auth
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 35/100
- Issue type
- Feature
- Clarity
- Mostly clear
- Activity status
- Stale
- Tech stack
- javascript, react, redux
- Domain
- api, authentication, frontend
Research direction
Start by tracing the Sign In button and the existing auth/ oauth1.js and oauth2.js providers for configurations without authentication settings. Review the proposed auth/none.js entry point and the README, then determine which UI state, authentication error handling, and documentation changes are in scope. Done means unauthenticated configurations no longer attempt OAuth and present the intended UI.
Written by the indexing model from the issue text.
Description
If we don't specify authentication settings in a configuration here is what happens after clicking the Sign In button:
WP.com
WP core (without OAuth1 plugin installed)
WP core (with OAuth1 plugin installed)
Next steps
- Maybe add a new auth provider
auth/none.jsand use it if the required parameters are not present - it doesn't make sense to have requests go throughoauth1.jsoroauth2.jsif we know there is no auth. - Detect this condition and make some UI changes accordingly (disable the Sign In button; maybe show an "unauthed" indicator instead).
- Add a note to the readme about this.
- Improve error handling for authentication requests in general.
- Dominant language
- JavaScript
- Stars
- 73
- Forks
- 23
- PR merge metrics
- No merged PRs in 30d
Getting set up
This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.
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.
More from Automattic/wp-api-console
-
Difficulty 4/5 3-5 days Newbie friendliness 25/100
Automattic/wp-api-console#120 ·
-
Difficulty 3/5 1-2 days Newbie friendliness 38/100
Automattic/wp-api-console#119 ·
-
bug
Difficulty 3/5 1-2 days Newbie friendliness 48/100
Automattic/wp-api-console#78 ·
-
question
Difficulty 3/5 1-2 days Newbie friendliness 25/100
Automattic/wp-api-console#77 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 35/100
Automattic/wp-api-console#68 · 3 comments ·
All issues in Automattic/wp-api-console
Similar issues
-
factory-active factory-automatic task-bug-reproduction-success task-identify-harness-labels-done task-identify-issue-type-done
Difficulty 2/5 1-3 hours Newbie friendliness 62/100
vercel/ai#22796 · 2 comments ·
Maintainers usually reply within 1 day
-
documentation
Difficulty 2/5 Half a day Newbie friendliness 78/100
facioquo/stock-indicators-dotnet#2300 ·
Maintainers usually reply within 1 day
-
good first issue needs-triage priority: low
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
melodic-software/claude-code-plugins#6982 · 1 comment ·
Maintainers usually reply within 1 day
-
val() setter uses the first control's type for a mixed selectionPossibly taken A pull request linked to this issue is open or already merged. Open
Difficulty 2/5 Half a day Newbie friendliness 85/100
Maintainers usually reply within 1 day
-
Difficulty 1/5 1-3 hours Newbie friendliness 75/100
douglascrockford/Misty#35 ·
Maintainers usually reply within 1 day