[5.x] Ability for relationship/entries fieldtype to add "hints" #10447
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 PR adds the ability for the relationship fieldtype to display "hints".
Hints are necessary when you have multiple options that could have the same value. For example if you have two entries in different collections with the same title, you don't know which is which:
The entries fieldtype already had this solved when in "stacked" mode because the collection is displayed as a column in the listing as well as having the collection title as a hardcoded hint in the selected item.
This PR makes the concept of these hints more generic across relationship fieldtypes.
This PR also improves the dropdown modes (select and typeahead) by adding hints and status icons to the dropdown options:
Lastly, this PR makes the selected items of the dropdown mode consistent with stacked mode:
Aside from a consistent UI, this allows the dropdown mode to have inline editing by clicking the item titles.
Replaces / Fixes #9749
Closes statamic/ideas#559
Allows #9229 to display the site name as part of the hint.