Skip to content
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

Add search filter support to assets #376

Closed
wants to merge 1 commit into from
Closed

Conversation

sunnavy
Copy link
Member

@sunnavy sunnavy commented Dec 19, 2023

No description provided.

@@ -56,7 +56,8 @@
</a>
</div>
<div class="modal-body">
% if ( $Attribute eq 'Subject' ) {
% if ( $Class eq 'RT::Tickets' ) {
% if ( $Attribute eq 'Subject' ) {
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looking at this file, I'm thinking it probably should have been originally created in share/html/Search/Elements. Do you recall why we put it in share/html/Elements?

To make this more readable, and thinking about eventually adding transactions, I wonder if we should put all of the RT::Tickets code in a new template share/html/Search/Elements/SearchFilterTickets, and RT::Assets in share/html/Search/Elements/SearchFilterAssets. Thoughts?

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think the initial reason we put it to "/Elements/SearchFilter" was that it's only called by "/Elements/CollectionAsTable/Header", but I agree that "/Search/Elements/" is more appropriate and I'll move it accordingly.

+1 to use different SearchFilter components

@bestpractical-mirror bestpractical-mirror deleted the 5.0/asset-search-filter branch December 21, 2023 14:55
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants