[TASK] Make page fields to select configurable via configuration for … #85
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.
…TreeMenu
Add the possibility to provide a list of page fields to select for the TreeMenu by setting e.g.:
pageFields = uid,pid,title,slug
The TreeMenu processor is a fast way to use it e.g. for an RESTful API. In order to create simpler API schemas it´s easier to define which fields are needed from pages. So the schema does not need to provide all ~100 fields if 5-6 are enough.
The change does not touch that nav_title, hasSubpages and subpages will be populated.