Add new field "accessor" to schema

[sahidvelji]

The name/key of the flag does not always make for a good variable name. Allow the user to optionally specify what the generated variable name should be for a flag using an "accessor" field in the flag manifest. An example is the hypothetical flag named "enable-api". In Go, this will generate a variable called EnableApi, which does not follow Go's initialism conventions: I would want to name it EnableAPI instead.

cli/internal/generators/golang/golang.tmpl

Line 25 in f260209

var {{ .Key | ToPascal }} = struct {

[beeme1mr]

I wonder if we should improve the string formatters to properly handle initialisms or acronyms. Your suggestion also seems like a good idea but the more we can automate, the better.

[beeme1mr]

@sahidvelji it actually looks like your exact example is covered 😆 but we may want to add more common initialisms and acronyms.

[sahidvelji]

it actually looks like your exact example is covered

Oh interesting. I couldn't get that to work correctly though.

I realize that the flag manifest file is meant to ideally be fetched and not handwritten. So I propose we use the config file for this purpose instead. So, we could have a default list of initialisms, but a user could add more initialisms in the config file if they see the need to do so. The staticcheck linter actually sort of takes this approach: https://golangci-lint.run/docs/linters/configuration/#staticcheck

[beeme1mr]

That's a good idea 👍

[Adityasinghvats]

Hey, I would like to work on this issue

[sahidvelji]

@Adityasinghvats I think we still need to flush out some details before this can be picked up.

@beeme1mr I'm thinking a new config file option initialisms that takes an array of additional initialisms beyond the builtin default ones that we define. Do we want this option to be available for Go only, or for all languages? I don't know what the conventions are for the other languages.

Here's an example config file where initialisms are specified for the Go generation only:

# Example .openfeature.yaml
manifest: "flags/manifest.json" # Overrides the default manifest path
generate:
  output: "src/flags" # Overrides the default output directory
  # Any language-specific options can be specified here
  # For example, for React:
  react:
    output: "src/flags/react" # Overrides the default React output directory
  # For Go:
  go:
    package: "github.com/myorg/myrepo/flags" # Overrides the default Go package name
    output: "src/flags/go" # Overrides the default Go output directory
    initialisms:
      - SQS
      - AWS
      - SNS