app-config

app-config copied to clipboard

Explore creating a Jest plugin

2

I would rather not point to "just mock the module" when asked how to test app-config.

joelgallant

Maybe in an `$env`, some value makes no sense - it would be nice to be able to, as a user, specifically fail with some error message.

joelgallant

Turns `true` to `false`, `-1` to `+1`

joelgallant

There is a gap in tests for checking that internal features are exposed to end users correctly. The unit tests of these features are decent, but any gaps when "putting...

joelgallant

Generated enums aren't accessible by code because they're embedded in type files, which aren't usually imported directly. Convert: ```typescript export enum MyType { Bar = 'bar', Baz = 'baz', Foo...

joelgallant

Create "Specification Tests" to ensure compliance of language code generation or libraries

1

As an offshoot of #46, we should have compliance tests to ensure that a library or code generation does the right thing. This is a bit hard to do, since...

joelgallant

Maybe looking at [dotenv](https://github.com/goatandsheep/react-native-dotenv/blob/main/index.js) plugin could help direct this.

joelgallant

Provide a generic mechanism for changing the config loading strategy

1

The `@app-config/config` module has a loading strategy baked-in. It would be awesome to describe that strategy "declaratively". This way, we can enable choosing different ConfgSources via the meta file.

joelgallant

We should have more unit testing and E2E testing for the plugin. Would be great to help with #123.

joelgallant

Robustly support schema references via URL

1

Detect and resolve `$ref` properties that point to http/s URLs. This is useful for databases like [schemastore](https://www.schemastore.org/json/). This would be implemented in `schema.ts`, in `resolveExternalSchemas`. Detect URLs like we detect...

joelgallant