docs(forms): document visibility handling in relationship condition with saveRelationshipsWhenHidden#19786
Merged
Merged
Conversation
danharrin
added
documentation
Added section on using visibility in condition functions for relationship data. Signed-off-by: Sngt25 <151845701+Sngt25@users.noreply.github.com>
Member
|
I made some tweaks in 059cd01 |
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
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.
Added section on using visibility in condition functions for relationship data.
Description
This PR adds documentation for using component visibility checks within relationship condition functions. It includes an example showing how to use
$component->isVisible()in the condition, and highlights the critical requirement of callingsaveRelationshipsWhenHidden()to preserve data when the component is hidden. This method is currently not indexed in the official docs, so the documentation provides important clarification.Visual changes
N/A - Documentation only update
Functional changes
composer cscommand.