[Edit] Switch other edit actions to mct-control #1204
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.
Went back to the edit menu cause it felt like I left the prev issue unfinished. Fixes #1198
There's a bit of a logic change. This here:
ng-class="{ major: $index === 0 && saveActions.length === 0 }"
Was not kept. Used to be
major: $index === 0
before the save button dropdown changes, but back then there was no separation between save actions and other actions, so I'm almost certain that it was just so that the save button shows up as major.Now that the save buttons show up as major anyway and are first in the menu, this doesn't seem to be useful anymore. It can only be useful if we have an edit context where we don't allow the user to save changes (no save actions available), which is something that doesn't make much sense (unless we add something like auto-saved objects?).
It can be brought back pretty easily if needed, via
cssclass: currentAction.getMetadata().cssclass + ($index === 0 && saveActions.length === 0 ? ' major' : '')
but if it's a condition that will/should never pass in practice, I'd rather we just removed it entirely.Thoughts?
Author Checklist
Changes address original issue? - Y
Unit tests included and/or updated with changes? - N/A, it's a markup change
Command line build passes? - Y
Changes have been smoke-tested? - Y