fix: correct query parsing for parentheses and AND/OR logic for filter logs

[ankita-gupta21]

Issue

https://gravitee.atlassian.net/browse/APIM-11728

Description

Fixes decodeQueryFilters to properly handle parentheses and maintain correct AND/OR precedence when parsing filter queries.

Additional context

• Fix decodeQueryFilters to properly split AND segments before processing OR
• Remove outer parentheses from segments before parsing
• Handle OR conditions within AND segments correctly
• Resolve issue where parentheses were included in split results

Fixes parsing of queries like:

• (api:123) AND (status:200) → ["api:123", "status:200"]
• (api:123) AND (status:200 OR status:429) → ["api:123", "status:200", "status:429"]

Before Fix

APIM-11728_Before-fix.mov

After Fix

Screen.Recording.2025-11-04.at.10.25.25.AM.mov

---

[gemini-code-assist]

Summary of Changes

Hello @ankita-gupta21, I'm Gemini Code Assist¹! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed!

This pull request resolves a critical issue in the log filtering mechanism by refining how complex queries involving parentheses and AND/OR logic are parsed. The changes ensure that filter conditions are correctly interpreted and applied, leading to more accurate and reliable log search results. Additionally, related UI components have been updated to handle array structures consistently and provide clearer user feedback.

Highlights

• Improved Query Parsing Logic: The decodeQueryFilters function has been enhanced to correctly interpret complex log filter queries, specifically addressing issues with parentheses and the precedence of AND/OR operators.
• Array Flattening for Filter Values: A new utility method, flattenArray, was introduced and integrated into the search-and-select component to ensure that filter values (like api, application, and status) are always stored as flat arrays, preventing nested array structures that could arise from complex query parsing.
• Enhanced UI Feedback for Search and Select: The search-and-select component now provides more accurate feedback to users, displaying 'No options available' when the options list is empty and no search term is active, rather than a generic 'Loading...' message.

Using Gemini Code Assist

The full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips.

Invoking Gemini

You can request assistance from Gemini at any point by creating a comment using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands on the current page.

Feature	Command	Description
Code Review	/gemini review	Performs a code review for the current pull request in its current state.
Pull Request Summary	/gemini summary	Provides a summary of the current pull request in its current state.
Comment	@gemini-code-assist	Responds in comments when explicitly tagged, both in pull request comments and review comments.
Help	/gemini help	Displays a list of available commands.

Customization

To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a .gemini/ folder in the base of the repository. Detailed instructions can be found here.

Limitations & Feedback

Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for Github and other Google products, sign up here.

You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension.

Footnotes

1. Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution. ↩

[gemini-code-assist]

Code Review

This pull request effectively fixes the query parsing for filters involving parentheses and complex AND/OR logic. The changes in logs-filters.controller.ts correctly handle the aggregation of filter values, and the defensive array flattening in search-and-select.controller.ts enhances the component's robustness. I've noted a potential issue in the filter value parsing that could lead to incorrect behavior, and I've also suggested a performance optimization for array handling. Please see my detailed comments below.