Add docs for some dynamically generated selectors in the core-data store #64269
Conversation
ryanwelcher
added
[Type] Developer Documentation
ryanwelcher
requested review from
ajitbohra,
juanmaguitar,
fabiankaegy and
ndiego
as code owners
|
The following accounts have interacted with this PR and/or linked issues. I will continue to update these lists as activity occurs. You can also manually ask me to refresh this list by adding the If you're merging code through a pull request on GitHub, copy and paste the following into the bottom of the merge commit message. To understand the WordPress project's expectations around crediting contributors, please review the Contributor Attribution page in the Core Handbook. |
|
This is the first of a few PRs of this type. I wanted to get this merged to see how it looks in the docs and perhaps allow for some other contributors to take part in this effort. |
| <!-- START TOKEN(Autogenerated selectors|../../../packages/core-data/src/selectors.ts) --> | ||
|
|
||
| ### canUser | ||
| #### canUser |
There was a problem hiding this comment.
Should this have been changed to an <h4> (####)? It appears to be a sub-heading for Selectors, which is an <h2>, and the other sub-headings above are all <h3>s.
Also, same question for the other sub-heading changes later. Otherwise, changes look good.
There was a problem hiding this comment.
Hmm. That seems odd. Those were all generated by doc gen. Let me look into it
What?
This PR manually adds documentation for the following dynamically generated selectors of the
core/datastore:getPostTypegetPostTypesgetTaxonomygetTaxonomiesPart of #64215
Why?
These are missed by the docgen tool and are much more user-friendly and docs are great :)