[Feature Request] global `@defaultSensitive=false` option

[bestickley]

Description

Pain point: I currently have to specify @defaultSensitive=false in my dozens of .env.schema files throughout my monorepo.

Motivation

I want to define it globally once. maybe like https://varlock.dev/reference/cli-commands/#packagejson-configuration ?

Proposed Solution

• package.json#varlock (but which package.lock in monorepo?) root?
• I could only set once in root .env.schema (which I import from everywhere) and then it propogates?

Alternatives

No response

Additional Information

No response

[philmillman]

Thanks for the request @bestickley and sorry for the pain. Those solutions seem reasonable. We'll discuss some options and get back to you soon!

[theoephraim]

• setting in package.json seems reasonable, although non-js projects wont have one, and we'd have to merge multiple settings in a monorepo
• project level config file (monorepo-root/.varlock/config.json) could make sense

But I think ideally this is expressed within the schema. The idea with not propagating it is that if you are breaking up schema into smaller files it kind of makes sense to apply root decorators to those items defined in the file only, and we dont really give your root .env.schema special treatment. Particularly makes sense if you are importing a vendor schema (ie define all VERCEL_* vars injected by the platform).

But maybe there's a way to mark the default as propagating, or to mark a specific import in a way that applies its root decorators to the current file.

Let us think on it a bit!

[bestickley]

thanks for quick response, guys! Maybe another idea: @defaultSensitive(sensitive=false, propagate=true)

[theoephraim]

totally! The only downside there is that currently decorator function calls (ie @fnName()) are used for things that are meant to be called more than once, while non-functions can only be called once.

So ideally it would be something that is part of the value, or perhaps some new kind of syntax which wraps the whole decorator.

Another thought is to change how defaults work, and make it more of a generic function call, something like @setDefault(sensitive, false, propagate=true). Fairly logical, but we lose out on some of the niceties of handling specific default things in different ways.