Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

WP.org: Missing namespaces from the dropdown

Open
  • Is something wrong?
#78 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
48/100
Issue type
Bug
Clarity
Clearly specified
Activity status
Stale
Tech stack
javascript, react, redux
Domain
api, frontend

Research direction

Reproduce the console locally against a WordPress REST API and compare the namespace dropdown with the root response's namespaces object. Trace how the dropdown options are populated; done means the custom namespace and oembed/1.0 appear alongside wp/v2.

Written by the indexing model from the issue text.

Description

bug

I'm using the console locally to interact with a localhost WordPress install. The namespace dropdown only lists wp/v2 and is missing both my custom namespace as well as oembed/1.0 which is built into core. Both of these are properly listed at the root of the REST API under the namespaces object.

firefox_2017-10-03_10-35-40 firefox_2017-10-03_10-39-37
Dominant language
JavaScript
Stars
73
Forks
23
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

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from Automattic/wp-api-console

All issues in Automattic/wp-api-console

Similar issues

More JavaScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.