OpenFeature’s official command-line tool
Go to file
Michael Beemer 4ae73cf019
bump version number
Signed-off-by: Michael Beemer <beeme1mr@users.noreply.github.com>
2024-10-04 13:57:05 -04:00
.github/workflows add release please 2024-10-04 13:55:18 -04:00
docs/schema/v0 refactor: change the case of the flag manifest to camel case. (#19) 2024-10-01 11:31:48 +00:00
sample feat: Fixing problems with generated code for golang and adding sample manifest for testing. (#22) 2024-10-03 07:59:09 +00:00
src feat: Fixing problems with generated code for golang and adding sample manifest for testing. (#22) 2024-10-03 07:59:09 +00:00
.gitignore feat: initial CLI for codegen with support for golang strongly typed accessors (#13) 2024-09-10 17:04:43 +00:00
.release-please-manifest.json bump version number 2024-10-04 13:57:05 -04:00
LICENSE
README.md
go.mod refactor: embed flag manifest schema into code and moves files around (#18) 2024-09-30 09:50:45 +00:00
go.sum refactor: embed flag manifest schema into code and moves files around (#18) 2024-09-30 09:50:45 +00:00
release-please-config.json add release please 2024-10-04 13:55:18 -04:00

README.md

OpenFeature Logo

OpenFeature CodeGen

work-in-progress Slack

[!CAUTION] OpenFeature CodeGen experimental! Feel free to give it a shot and provide feedback but expect breaking changes.

OpenFeature is an open specification that provides a vendor-agnostic, community-driven API for feature flagging that works with your favorite feature flag management tool or in-house solution.

Why CodeGen?

CodeGen automates the creation of strongly typed flag accessors, minimizing configuration errors and provides a better developer experience. By generating these accessors, developers can avoid issues related to incorrect flag names or types, resulting in more reliable and maintainable code.

Goals

  • Unified Flag Manifest Format: Establish a standardized flag manifest format that can be easily converted from existing configurations.
  • Strongly Typed Flag Accessors: Develop a CLI tool to generate strongly typed flag accessors for multiple programming languages.
  • Modular and Extensible Design: Create a format that allows for future extensions and modularization of flags.

Non-Goals

  • Full Provider Integration: The initial scope does not include creating tools to convert provider-specific configurations to the new flag manifest format.
  • Validation of Flag Configs: The project will not initially focus on validating flag configurations for consistency with the flag manifest.
  • General-Purpose Configuration: The project will not aim to create a general-purpose configuration tool for feature flags beyond the scope of the codegen tool.

Support the project

Thanks to everyone who has already contributed

Pictures of the folks who have contributed to the project

Made with contrib.rocks.