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

Fixes #38252 - Handle boolean searchable_value displayed as true/false in search field #10462

Open
wants to merge 1 commit into
base: develop
Choose a base branch
from

Conversation

lfu
Copy link
Contributor

@lfu lfu commented Feb 27, 2025

searchable_value is a text field in DB. So boolean value is saved as t and f in the DB instead of true and false.

Test Steps
Hosts - Content Hosts, and in the search field, you can add a query

Before
params.host_registration_insights = f and params.host_registration_insights = false
Both "false" and "f" will be presented automatically on Satellite . But you get accurate response only when selecting "f".

If you don't see params.host_registration_insights = false displayed on your server, just add a global parameter with string type and false value.

After
Both params.host_registration_insights = false or params.host_registration_insights = f would work with the same result.

@lfu lfu marked this pull request as draft February 27, 2025 22:08
@lfu lfu force-pushed the 22655_params_host_registration_insights branch from fe2e792 to 8aadda2 Compare February 28, 2025 18:48
@lfu lfu changed the title Fixes #38252 - Display boolean searchable_value as true/false in search field Fixes #38252 - Handle boolean searchable_value displayed as true/false in search field Feb 28, 2025
@lfu lfu marked this pull request as ready for review February 28, 2025 20:04
@lfu
Copy link
Contributor Author

lfu commented Mar 10, 2025

Could someone take a look at this?

@stejskalleos stejskalleos self-assigned this Mar 18, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants