Add custom sorting documentation #770
Merged
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
Use the ProviderConfiguration from the parent and set/overwrite values using setters.
…hiasseghers/sulu-docs into smartcontent-custom-sorting
matthiasseghers
force-pushed
the
smartcontent-custom-sorting
branch
from
e7c1fd6
to
573756a
Compare
|
@matthiasseghers thank you! |
martinlagler
pushed a commit
to martinlagler/sulu-docs
that referenced
this pull request
Feb 13, 2024
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.
What's in this PR?
Adds a section that explains how to customize the fields of smart_content that are displayed on the admin side. By making small adjustments, you can change the configuration without having to write a custom data provider with a custom entity. This can be particularly helpful when sorting needs to be done on a custom property for one of the types, or when certain functionality is fixed. For instance, you may want to overwrite the sorting method without giving the option to overwrite it with a custom QueryBuilder. These changes to the documentation file are meant to clarify and simplify the process of customizing smart_content fields on the admin side.
Why?
The documentation currently doesn't mention that certain parts of the DataProvider can be overwritten to make minor changes to the configuration without having to create a custom data provider. Additionally, it doesn't explain how to sort by a custom property based on one of the templates.