Antonio

Results 254 comments of Antonio

I moved this issue to on hold state, because the solution is a POC based in a workaround.

Hi @ArielIvanOjeda , this issue is on hold because the workaround to get the available fields in each API endpoint doesn't match in some use cases. For example, some current...

I was researching a problem with a particular API search in the Wazuh plugin. When the value of search query parameter contains `&`, the API replies that is not a...

According to the @vicferpoy , the `search` query parameter has a regex restriction. ```python _search_param = re.compile(r'^[^;|&^*>]+$') ``` ![image](https://user-images.githubusercontent.com/34042064/217207034-a68384ad-afb3-4aed-aef9-42aa7d5a2bc1.png) ![image](https://user-images.githubusercontent.com/34042064/217207208-ffdaf6bf-ba3f-4389-a44f-7e354140b4e5.png) The `search` query parameter doesn't support `&` or `;` characters....

According to @davidjiglesias , we could use the `q` query parameter instead to do the `search`. Another issue suggesting this approach: https://github.com/wazuh/wazuh-kibana-app/issues/5198

We move this issue to 4.5.0 because it needs some changes in the search bar and there is an epic issue https://github.com/wazuh/wazuh-kibana-app/issues/4312 to redo it.

**thought**: Personally, I don't like the usage of the `ErrorOrchestrator` service. It looks overcomplicated to me.

**praise**: Good job adding some documentation about error management.

**thought**: I feel we should discuss how we want to manage the errors and the required implementation.