Skip to content

Conversation

@pquentin
Copy link
Member

@pquentin pquentin commented Nov 6, 2025

I'm not including descriptions for now, this will be next step. I'm hopeful that the Docs team can help me for that.

Is the way I've added enums specific to an API in the Request files OK?

@pquentin pquentin added the skip-backport This pull request should not be backported label Nov 6, 2025
@github-actions
Copy link
Contributor

github-actions bot commented Nov 6, 2025

Following you can find the validation changes against the target branch for the APIs.

API Status Request Response
cluster.state 🟢 → 🔴 85/85 → 84/85 84/84
nodes.stats 🔴 58/58 → 39/58 21/58

You can validate these APIs yourself by using the make validate target.

sparse_vector
}

export type CommonStatsFlags = CommonStatsFlag | CommonStatsFlag[]
Copy link
Member

Choose a reason for hiding this comment

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

Could we please introduce an alias like this in all the other places as well instead of inlining the "single or many"?

This would allow me (and potential other consumers) to translate this construct into a native C# Flags enum for improved usability.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

skip-backport This pull request should not be backported specification

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants