3 ms·
I think config _is_ the clear boundary between those gathering, ordering etc steps. The less expressive config is, the more regular and structured it is, and i
by dwattttt 2y ago
I think config _is_ the clear boundary between those gathering, ordering etc steps.
The less expressive config is, the more regular and structured it is, and it becomes very easy to be descriptive and composable.
- pas 2y agofrom time to time config is just not willing to sit there in a list. it needs to be computed. just an example from a few days ago. someone needs to pull data from some remote service (maybe Vault), or generation of keys/entropy/etc. [0][1] of course this just means folks should wrap the whole thing in a program. but that's getting inefficient fast if every layer only accepts "env vars" or a plain JSON file. [0] https://github.com/nextauthjs/next-auth/pull/9638#issuecomment-2105161063 https://github.com/nextauthjs/next-auth/pull/9638#issuecomme... [1] https://github.com/nextauthjs/next-auth/pull/9638#issuecomment-2184292582 https://github.com/nextauthjs/next-auth/pull/9638#issuecomme...