[Beats CM] Re-arch table assignment control definitions #23663
Merged
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.
Changes
The goal of these changes is to simplify the definition of assignment options for tables, and to make the components that handle the options and their associated actions more generic.
The layout and associated properties of the assignment options can now be defined like this:
Any objects and an action handler are specified at the declaration of the table component:
There're three ways to display assignment options:
none
:There are no controls displayed for the table.
primary
:When items are selected, the option is displayed next to the normal controls. This is appropriate when the controls perform actions only on the selected objects.
assignment
:When items are selected, the actions replace the normal controls. This is appropriate when there will be association between the table's selected objects and some other list of objects or resources.