Hacktoberfest 2026: los issues que los mantenedores marcaron para octubre, abiertos y aptos para principiantes. Explorar issues de Hacktoberfest

Code Generation

Abierto
#32 0 comentarios 0 reacciones 2 asignados Ver en GitHub

@anghelflorinm ya está trabajando en esto.

Desde el 17/10/2024.

Evaluación

Este issue todavía no se ha evaluado.

Descripción

epic

Description

Feature flags typically rely on hard coded strings to reference specific feature flags. This can be tedious to maintain in a codebase. Code generation can address this shortcoming by creating strongly typed flag accessors, minimizing configuration errors and providing 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

  • Establish a standardized flag manifest format that can be easily converted from existing configurations.
    • JSON Schema (source of truth)
    • Auto-gen docs from schema and clarifying docs
  • Develop a CLI tool to generate strongly typed flag accessors for multiple programming languages.
    • Create support for Java, JavaScript, Go, and Markdown
  • Create a format that allows for future extensions and modularization of flags.
    • Simply adding support for new languages
      • Reduce boilerplate
      • Standardize templates format
  • Create contributing documentation

Non-goals

  • The initial scope does not include creating tools to convert provider-specific configurations to the new flag manifest format.
  • The project won't initially focus on validating flag configurations for consistency with the flag manifest.
    • Create prototype prior to a stable release
  • The project does not aim to create a general-purpose configuration tool for feature flags beyond the scope of the codegen tool.

Resources

Lenguaje dominante
Go
Estrellas
63
Forks
22
Merge medio
1 h 27 min
PR fusionados (30 d)
19

Guía de contribución

Abrir la guía de contribución

Primeros pasos

  1. Lee el issue completo y luego la guía de contribución del proyecto.
  2. Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
  3. Haz un fork del repositorio y trabaja en una rama.
  4. Abre un pull request que haga referencia al número del issue.

Más de open-feature/cli

Todos los issues de open-feature/cli

Issues similares

Más issues de Go

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.