Skip to content

Conversation

@kwilczynski
Copy link
Contributor

Even though the data.result query parameter can be added when calling the /events endpoint, add the result parameter for convenience.

This will also shorten the entire query and hide some of the internal implementation details from the end-user, as in the future, the query parameters might be sanitised such that any unknown or unsupported values could be removed.

Even though the "data.result" query parameter can be added when calling
the "/events" endpoint, add the "result" parameter for convenience.

This will also shorten the entire query and hide some of the internal
implementation details from the end-user, as in the future, the query
parameters might be sanitised such that any unknown or unsupported
values could be removed.

Signed-off-by: Krzysztof Wilczyński <krzysztof.wilczynski@collabora.com>
@kwilczynski kwilczynski self-assigned this Apr 21, 2025
@kwilczynski kwilczynski requested a review from nuclearcat April 21, 2025 09:36
Copy link
Member

@nuclearcat nuclearcat left a comment

Choose a reason for hiding this comment

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

Thanks a lot Krzysztof, looks good!

@nuclearcat nuclearcat added this pull request to the merge queue Apr 21, 2025
Merged via the queue into kernelci:main with commit 4111a4b Apr 21, 2025
4 checks passed
@kwilczynski kwilczynski deleted the feature/add-result-filter-to-events-endpoint branch April 21, 2025 10:12
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