Closed Nov 14, 2023
No due date
•Closed This is a tracker for all the issues with bad/missing results when resolving nodes by their URI.
The general problem stems from NodeResolver's attempt to replicate WP::parse_request with a provided uri. Assumingly, some of these are due to misordered conditionals, while others are missing edge cases.
Proposed Work
As I see it, the ideal solve requires 3 steps:
- #2342 Refactor
NodeResolverto make the code less complex, and easier to test/iterate on. - Add missing
wpunittests toNodeByUriTestto bringNodeResolver::resolve_uri()to 100%. - Research and add support for other edge cases, using the issues below as a baseline.
Tracking:
- #2394
- #2191
- #2190
- #2178
- #2091
- #2066
- #1910
- #1850
- #1712
- #1687
- #1673
- #1639
If I missed an issue or if you have a use case not referenced by an existing issue, please share and I'll add it to the tracker.
91% complete
List view
0 issues of 1 selected
- Status: Open.#2191 In wp-graphql/wp-graphql;