devin ivy

Yeah, would totally accept docs on the CLI! 👍

If we decide we want to go forward with this, I have a proposal here: https://github.com/hapipal/confidence/pull/110 I thought that removing `$env` left a small gap, so in that proposal I...

Worth noting that there was some chatter in hapi hour about this, mostly concerns that removing `$env` would make things less explicit than it currently is, and that some folks...

I believe that currently no way to do that: you'd have to push that logic down into the params that you pass to the store. But in my opinion it...

I wonder if one way to speak to this would be to allow the user to provide a function with their logic within the schema. The function would be passed...

If there are no other proposals, I would take a PR for `$fn` 👍

I am actually a fan of envy. If we did decide to go that direction, could we contribute to update envy's tests for some recent versions of node? (I realize...

@sholladay I am playing with envy in a baseline pal boilerplate, and am running into an issue I can't resolve myself: the boilerplate only has one env variable (`PORT`) which...

Just an update here for those interested: I am favoring an eventual move to envy, but there are some loose ends regarding Windows support that are still in progress, and...

Hey, thanks for this! I appreciate you moving the ball forward on this long-standing issue. Here's the basic acceptance criteria: - [x] Providing `--no-color` or `--color` as an argument should...