-
Notifications
You must be signed in to change notification settings - Fork 178
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Improvements to API Reference #830
Conversation
Standing this up for feeback. While it does have pretty obvious UX disadvantages, it draws a clearer distinction and provides more detail in the docs. * Promote API link to header menu * Serve HTML API docs out of public dir - if we stick to this we'll want to clean up the URLs with Next redirects or something similar.
See /api/classes/NextDrupal.html#getresource for output
Not positive if we want to ignore this, or just find a way to re-order this in menus.
The latest updates on your projects. Learn more about Vercel for Git ↗︎
2 Skipped Deployments
|
@@ -294,6 +294,62 @@ export class NextDrupal extends NextDrupalBase { | |||
* @param {string} uuid The UUID of the resource. | |||
* @param {JsonApiOptions & JsonApiWithCacheOptions & JsonApiWithNextFetchOptions} options Options for the request. | |||
* @returns {Promise<T>} The fetched resource. | |||
* @examples |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This examples diff was made by feeding the markdown from the old reference section to Copilot, which made this waaaay less tedious.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Nice! This looks really good.
This pull request is for: (mark with an "x")
examples/*
modules/next
packages/next-drupal
starters/basic-starter
starters/graphql-starter
starters/pages-starter
GitHub Issue: #829
Please add a link to the GitHub issue
where this problem is discussed.
Describe your changes
More detail in the issue, but this PR is attempting to bridge the gap between our old API reference section and the new autogenerated API docs.
This would also be a reasonable home for any final documentation updates related to the 2.x stable release.