This pull request is a follow-up to #3137 to give the flexibility for inherited plugins (i.e. time selector in lcviz or cube extraction in lcviz/rampviz) to override the plugin key shown in the API hints. It also makes the following small tweaks:
fix the styling on a component in the slice plugin
fix styling for "apply RGB presets" button in plot options
fix options for "align_by" in orientation plugin to be the same options as the API
add quotes around the color string in color picker
Change log entry
[x] Is a change log needed? If yes, is it added to CHANGES.rst? If you want to avoid merge conflicts,
list the proposed change log here for review and add to CHANGES.rst before merge. If no, maintainer
should add a no-changelog-entry-needed label.
Checklist for package maintainer(s)
This checklist is meant to remind the package maintainer(s) who will review this pull request of some common things to look for. This list is not exhaustive.
[x] Are two approvals required? Branch protection rule does not check for the second approval. If a second approval is not necessary, please apply the trivial label.
[ ] Do the proposed changes actually accomplish desired goals? Also manually run the affected example notebooks, if necessary.
[ ] Are tests added/updated as required? If so, do they follow the STScI Style Guides?
[ ] Are docs added/updated as required? If so, do they follow the STScI Style Guides?
[ ] Did the CI pass? If not, are the failures related?
[x] Is a milestone set? Set this to bugfix milestone if this is a bug fix and needs to be released ASAP; otherwise, set this to the next major release milestone. Bugfix milestone also needs an accompanying backport label.
[ ] After merge, any internal documentations need updating (e.g., JIRA, Innerspace)?
Description
This pull request is a follow-up to #3137 to give the flexibility for inherited plugins (i.e. time selector in lcviz or cube extraction in lcviz/rampviz) to override the plugin key shown in the API hints. It also makes the following small tweaks:
Change log entry
CHANGES.rst
? If you want to avoid merge conflicts, list the proposed change log here for review and add toCHANGES.rst
before merge. If no, maintainer should add ano-changelog-entry-needed
label.Checklist for package maintainer(s)
This checklist is meant to remind the package maintainer(s) who will review this pull request of some common things to look for. This list is not exhaustive.
trivial
label.