-
-
Notifications
You must be signed in to change notification settings - Fork 824
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
SavedSearch - Add name and label columns #18809
Conversation
(Standard links)
|
@seamuslee001 @eileenmcnaughton @totten this is going to go stale real fast. |
</index> | ||
|
||
<field> | ||
<name>label</name> |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Does this need "localizable"?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
No I don't think so. This is intended for back-end administration screens.
1a71549
to
53b13ff
Compare
Test fails were being caused by the sloppy function |
@eileenmcnaughton I forgot to add the unique index to the upgrader. Looking at the function |
@colemanw only manually |
Overview
Adds 2 database columns:
name
andlabel
for the SavedSearch entity.This is needed by the new Search Kit extension.
Before
SavedSearch
entity lacks unique name or label.Pre/post hooks not called for SavedSearch entity.
After
Label column added for identifying saved search on administrative screens.
Unique name column added for embedding savedsearch displays by name on pages, dashlets, etc.
Pre/post hooks called.
Technical Details
Unique name generated from label if not supplied.
Switching from ad-hoc create function to the standard
dao::writeRecord
ensures that hooks are properly called.