Marc J. Schmidt
Marc J. Schmidt
To have a better overview of this issue: - [Open, unlikely] Breaking up large queries - [Open] Adding aggregate columns to SELECT inside of a join (useJoin/useInnerJoin) - [Open] Create...
I think that we should not anything to the query API that SQL is capable of, that would be way too much. We can surely add here and there new...
this is implemented, see https://deepkit.io/documentation/orm/raw-access
I'll leave this example and close this issue as there is nothing to do: https://github.com/deepkit/deepkit-framework/blob/master/packages/type/tests/serializer-api.spec.ts#L47-L65
I think this is very outdated and not needed anymore. I'm going to close this, but feel free to reopen if it is still relevant.
Naming strategy was implemented a long time ago. I'm going to close this, but feel free to reopen if anything else needs to be addressed.
Async de/serialization is not going to happen as it would break many APIs and core functionality. I'm going to close this, but we can address this again in the future...
https://github.com/hanayashiki/deepkit-openapi can create json schema files from TS types.
Here is an example that shows how a custom class type can be de/serialised: https://github.com/deepkit/deepkit-framework/blob/master/packages/type/tests/serializer-api.spec.ts#L48-L64 I'll close this issue since I don't see anything we can do.
Please provide a pull-request, so I can merge.