feat: persist project config in deno.json

[arnauorriols]

No description provided.

[magurotuna]

My understanding is that it reads a config file and merges it to Args. But I'm a little bit concerned with this approach because Args is just a parsed result of std's parse function, which doesn't have any domain knowledge of individual applications.

What I'd like to propose is to define a new class/object that stores all configurable values (which I'll call Config) and construct Config from the config file, command line args, and even env vars, then we'll be able to use the Config instance throughout the process.

[arnauorriols]

My understanding is that it reads a config file and merges it to Args. But I'm a little bit concerned with this approach because Args is just a parsed result of std's parse function, which doesn't have any domain knowledge of individual applications.

What I'd like to propose is to define a new class/object that stores all configurable values (which I'll call Config) and construct Config from the config file, command line args, and even env vars, then we'll be able to use the Config instance throughout the process.

I don't disagree, but I'd rather do it in a separate PR, as this work would be orthogonal to the scope of this PR. I've created the issue #196 for it

[magurotuna]

Question: will we add support for JSONC later?

[arnauorriols]

Question: will we add support for JSONC later?

that's the plan, yes. I've created an issue also for this to keep track of it: #198

[satyarohith]

LGTM apart from the minor comments