document field inputs #273
Closed
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
zachdaniel
approved these changes
Jan 13, 2025
Contributor
|
🚀 Thank you for your contribution! 🚀 |
Contributor
|
Looks like I dropped the ball on this and its been documented in a different way since. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
I added support for this query parameter a while back but recently realized it's never been documented anywhere in the ash_json_api docs, so it's just kind of an obscure easter egg for those who read the source code, or come asking those who know about it on the discord 😅 so this adds some really simple docs for it in the non-spec query params section of the docs.
Contributor checklist
- [ ] Bug fixes include regression tests- [ ] Features include unit/acceptance tests(N/A)