Joe

I would love to but I haven't been able to figure out the root issue. Our current workaround is to cast it to `FastifyInstance` ```typescript export const handler = fastifyLambda(app...

Worked like a charm! Much appreciated 🙏

I shamelessly took the work done by @DesignByOnyx and added a bit of typescript, didn't need manual directory tree (maybe it was bug in `jszip` or something from earlier version),...

Marking a property as optional (using `?`) means it can possibly be `undefined`. `undefined !== null` Did you try something like ```typescript class Foo extends Model { // ... @Attribute(DataTypes.ARRAY(DataTypes.STRING))...

> Is there any point in making it optional? The biggest imo is it's still marked experimental. It is opt-in and should remain _explicitly_ opt-in until it's part of stable...

Anything I can help out on to get this merged in?

@brianespinosa know anyone with repo write access that can review (and approve) this?

@styfle thanks for pointing those out, it's definitely worth noting. My 2 cents: those do seem far away from reaching social consensus (there's still ongoing debate as of hours ago),...

@dpattmann commits squashed. Note I have not been able to test this yet.