Marc J. Schmidt

Oh, good catch, yes that's right! JSON fields should not use the database serializer.

`asName` is only for necessary when code is minimized (constructor argument names are usually changed then, which would make getting fields as constructor args impossible, and thus strict mode impossible)....

Constructor with `asName` is not a great replacement for your need. Better is to way for the weekend, then I think we figured something out.

I thought about that and I think that this feature pretty much makes the whole codebase of converting, validation, property definition way too complex. It's probably easier to write a...

PostGIS is not implemented yet. I've never used it, so not sure how the ORM API would look like to support it. JSONB is supported, but it depends on how...

This violates separation of concerns and is thus very unlikely to happen. Fetching data should happen before serialization. Why do you need that process **while** serializing? You can always write...

First version has been added here https://github.com/deepkit/deepkit-framework/commit/3088e829c89e09d7621eb916501877344064e8a8

@freddi301 cool idea! If we can get it very fast, we could replace the primary key hashing of the ORM https://github.com/deepkit/deepkit-framework/blob/master/packages/type/src/snapshot.ts#L153-L159 If you want to create a PR that would...

I think we have to adjust https://github.com/deepkit/deepkit-framework/blob/master/packages/http/src/model.ts#L179 in order to make it compatible with the request object interface required by those middlewares.

I wonder though why in the stack trace is express code `node_modules/.pnpm/[email protected]/node_modules/express/lib/router/layer.js:95`. Are you using express and Deepkit at the same time?