FIX Make child responsible for its own nested gridfield #393
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.
Currently the parent is responsible for dictating how the child's nested gridfield should be configured. This change allows the child to determine that for themselves.
Code before this PR to get nested gridfields
Code after this PR to get nested gridfields
Other change made
This also passes in some information to the
getNestedConfig()
method which can be used to decide how to display itself. For example, a class which has theHierarchy
extension might want to always list itself as a nested child, but doesn't want to override the default code for that. It could be implemented like so:Issue
getNestedConfig()
called on the parent but should be called on the child #394