[7.x] Refactor the fieldtype model selector #592
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
This means it'll use the columns from a user's column preferences.
…digital/runway into fix/fieldtype-model-selector
|
Released as part of v7.9.0. |
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.
This pull request does some refactoring around the Models Selector in Runway's built-in fieldtypes.
Instead of returning arrays from the
getIndexItemsmethod, it'll return the models, which will then be transformed by JSON resources. This follows how Statamic works with the Entries fieldtype.It'll also pull the columns for the models selector from the user's preferences, if they have any set, rather than always using the default listable columns from the resource's blueprint.
Fixes #588.