Skip to content

Conversation

@ggivo
Copy link
Collaborator

@ggivo ggivo commented Nov 4, 2025

No description provided.

@ggivo ggivo changed the title Topic/ggivo/command flags (clean up) Sepate generated command flags registry initialisation from actual implementation Nov 5, 2025
@ggivo ggivo changed the title (clean up) Sepate generated command flags registry initialisation from actual implementation (clean up) Separate generated command flags registry initialisation from actual implementation Nov 5, 2025
@ggivo ggivo marked this pull request as ready for review November 5, 2025 07:37
@uglide uglide merged commit bb7bb39 into im/introduce-command-flags Nov 5, 2025
6 checks passed
@uglide uglide deleted the topic/ggivo/command-flags branch November 5, 2025 08:57
uglide added a commit that referenced this pull request Nov 5, 2025
* Add commands flags based on static map

* Clean up CommandFlagsRegistryGenerator

* more fixes to CommandFlagsRegistryGenerator

* Introduce CommandFlagsRegistry interface

- Add new interface and move CommandFlag enum there
- Generate StaticCommandFlagsRegistry instead of embedding generated code into CommandObject
- Allow passing custom CommandFlagsRegistry to ClusterClientBuilder

* Fix formatting

* Add support for sub-commands

* Use CommandArguments in the interface and hierarchical approach in static registry

* Expose get() on CommandArguments for cleaner code

* Use byte array based look up to improve performance

* (clean up) Separate generated command flags registry initialisation from actual implementation (#4345)

* (clean up) Extract generated registry initialization

* regenerate after clean up

* reformat

* Clean up StaticCommandFlagsRegistry

---------

Co-authored-by: Ivo Gaydazhiev <ivo.gaydazhiev@redis.com>
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.

3 participants