Update Field::HasOne options documentation #2375
Merged
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
nickcharlton
approved these changes
Apr 30, 2023
Member
nickcharlton
left a comment
nickcharlton
left a comment
There was a problem hiding this comment.
Thanks!
Can we split out the heading change into another PR? I wonder if it's worth seeing if other pages have the same problem when doing that too. What do you think?
Contributor
Author
Sure, will do! |
littleforest
force-pushed
the
update-has-one-docs
branch
from
3a7576a to
47e78c3
Compare
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.
This updates the documentation for customizing the
Field::HasOnewith theorderoption, which was added in #2325. This also changes each of the field descriptions to an h4 tag for better accessibility and to provide links to those headers.