How can I have an environment-controllable value that defaults to true?

[djMax]

This is easy with a default of false:

{
   "enable_something": "env:SOME_ENV_VAR|b",
   "meddleware": {
      "something": {    
         "enabled": "config:enable_something"
      }
   }
}

But how can it be arranged to default to true? This is potentially a confit/shortstop thing more than a meddleware thing, though I can see changes to any of them to fix it.

[shaunwarman]

Hey @djMax

You're right. You'd want to use confit to load your json configuration that uses confit's protocol option to pass in your custom shortstop protocol.

There is a similar setup in the tests here, but you would want to probably take it further and have confit do the work of loading the json and taking advantage of your custom shortstop protocol. Then you can pass that object to meddleware.

Additionally, the shortstop protocol would look very similar to the default env handler in shortstop-handlers.

It's late, but I'll create an example in the AM.

[shaunwarman]

So here's a simple example using a new shortstop handler:
https://github.com/shaunwarman/custom-confit-shortstop-example

This new handler would need to be passed to confit options like mentioned above and used to resolve your config file. Then this config object can get passed to meddleware at startup.

[djMax]

Yes, I can definitely see how to do it with a shortstop, but this feels like something that shouldn't require one... Basically there is support for "true" as default, but not false. Weird.