François Best's latest activity
@paul out of curiosity, why not delete the attachment altogether after the email is sent?
Is there value in keeping them for forensics?
…See more
@paul out of curiosity, why not delete the attachment altogether after the email is sent?
Is there value in keeping them for forensics?
See less
@paul out of curiosity, why not delete the attachment altogether after the email is sent?
Is there value in keeping them for forensics?
@paul out of curiosity, why not delete the attachment altogether after the email is sent?
Is there value in keeping them for forensics?
…See more
See less
@dansup not sure about fedilebrity, I half-dyslexically read that as febrility.
…See more
@dansup not sure about fedilebrity, I half-dyslexically read that as febrility.
See less
@dansup not sure about fedilebrity, I half-dyslexically read that as febrility.
@dansup not sure about fedilebrity, I half-dyslexically read that as febrility.
…See more
See less
@paul @pdenya I've encountered a similar use-case when loading environment variables, validating them and exposing the result to the rest of the application.
Here's how I go about doing it, using Zod for parsing and transforming, and crashing early with helpful messages if something isn't right.
https://github.com/SocialGouv/e2esdk/blob/beta/packages/server/src/env.ts
Though the resulting env object is exported/imported rather than passed as arguments, in Fastify I could expose it as a server property and use that as dependency injection.
…See more
@paul @pdenya I've encountered a similar use-case when loading environment variables, validating them and exposing the result to the rest of the application.
Here's how I go about doing it, using Zod for parsing and transforming, and crashing early with helpful messages if something isn't right.
https://github.com/SocialGouv/e2esdk/blob/beta/packages/server/src/env.ts
Though the resulting env object is exported/imported rather than passed as arguments, in Fastify I could expose it as a server property and use that as dependency injection.
See less
@paul @pdenya I've encountered a similar use-case when loading environment variables, validating them and exposing the result to the rest of the application.
Here's how I go about doing it, using Zod for parsing and transforming, and crashing early with helpful messages if something isn't right.
https://github.com/SocialGouv/e2esdk/blob/beta/packages/server/src/env.ts
Though the resulting env object is exported/imported rather than passed as arguments, in Fastify I could expose it as a server property and use that as dependency injection.
@paul @pdenya I've encountered a similar use-case when loading environment variables, validating them and exposing the result to the rest of the application.
Here's how I go about doing it, using Zod for parsing and transforming, and crashing early with helpful messages if something isn't right.
https://github.com/SocialGouv/e2esdk/blob/beta/packages/server/src/env.ts
Though the resulting env object is exported/imported rather than passed as arguments, in Fastify I could expose it as a server property and use that as dependency injection.
@paul Passing it as a parameter makes the modules much easier to test under different configurations, so I'd go for that.
I'd also type the config arguments as `Pick<ConfigType, 'whatever' | 'keys' | 'are' | 'needed'`>`, to limit the amount of boilerplate/mock needed in tests.
…See more
@paul Passing it as a parameter makes the modules much easier to test under different configurations, so I'd go for that.
I'd also type the config arguments as `Pick<ConfigType, 'whatever' | 'keys' | 'are' | 'needed'`>`, to limit the amount of boilerplate/mock needed in tests.
See less
@paul Passing it as a parameter makes the modules much easier to test under different configurations, so I'd go for that.
I'd also type the config arguments as `Pick<ConfigType, 'whatever' | 'keys' | 'are' | 'needed'`>`, to limit the amount of boilerplate/mock needed in tests.
@paul Passing it as a parameter makes the modules much easier to test under different configurations, so I'd go for that.
I'd also type the config arguments as `Pick<ConfigType, 'whatever' | 'keys' | 'are' | 'needed'`>`, to limit the amount of boilerplate/mock needed in tests.