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

Refactor SearchTextField with SearchHistorySupport interface #175

Closed
wants to merge 1 commit into from

Conversation

leewyatt
Copy link
Contributor

Updated SearchTextField to implement SearchHistorySupport interface, improving modularity and extendability. Removed SearchTextFieldHistoryPopup in favor of more generic SearchHistoryPopup. Renamed related popup skin class and updated references accordingly. Also, created new 'search-history-popup.css' for styling and cleared some unused styles in 'search-text-field.css'.

Updated SearchTextField to implement SearchHistorySupport interface, improving modularity and extendability. Removed SearchTextFieldHistoryPopup in favor of more generic SearchHistoryPopup. Renamed related popup skin class and updated references accordingly. Also, created new 'search-history-popup.css' for styling and cleared some unused styles in 'search-text-field.css'.
Copy link

Quality Gate Failed Quality Gate failed

Failed conditions
0.0% Coverage on New Code (required ≥ 80%)

See analysis details on SonarCloud

@dlemmermann
Copy link
Collaborator

I don't like the interface approach in this PR. I think we are trying to hard to find the common parts of two controls that are very differently structured. I think a better approach would be to have the node showing the magnifying class and the down arrow to encapsulate the common logic and to reuse that for both fields. Then the two fields could implement an interface like "HistoryProvider".

@leewyatt leewyatt closed this May 11, 2024
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.

2 participants