reorganize info on channel entry variables and add information about custom fields #585
Conversation
This file contains 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
TomJaeger
previously requested changes
Mar 2, 2023
There was a problem hiding this comment.
I think the channel/entries.md file changes we should hold off on for now. The rest look good to me. @intoeetive can you break the channel entries changes out?
|
@TomJaeger yes - here's the new PR #591 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
The main objective of this PR was to re-organize the variable provided by
exp:channel:entriesinto logical groups, so people could easier find what they need instead of having to scroll through the full listI also added a bit more information about how the custom fields should be assigned and used
Lastly, fixed some broken links and images