Replies: 1 comment
-
yeah absolutely. If you want, please contribute this? |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
Certainly there are already a lot of JSDoc comments in the code base providing helpful documentation especially handy inside IDEs that surface those. But there are also a lot of things that don't have JSDoc comments where they would definitely be useful.
For example, compare all the helpful information in the
useQuery
docs for all the query options to the JSDocs available for the query options:query/packages/query-core/src/types.ts
Lines 70 to 80 in 3643b87
Even less information is available when comparing the docs for the return type to what is available in the JSDoc comments:
query/packages/query-core/src/types.ts
Lines 374 to 402 in 3643b87
This means I often have to leave my IDE, open up the docs website, make sure I switch to the correct version of the docs, then find the documentation for the thing I'm trying to use. In my ideal world the JSDoc comments would serve as a sort of source of truth from which the documentation website would be derived, but that's probably a big ask.
Instead I'd just ask that more of the information available in the docs could be also made available in JSDoc comments and/or have JSDoc comments linking back to the official docs:
Side request: provide more anchors/ids for parts of the docs so we can link directly to stuff like the
QueryOptions.isDataEqual
instead of only being able to link touseQuery
and then ask the person to search for "isDataEqual".Beta Was this translation helpful? Give feedback.
All reactions