Martin Adámek
Martin Adámek
The `replicate` method from laravel seems to be doing something else, its for cloning an existing model you have in memory, this issue is about firing a query and handling...
I guess I would rather go with the second approach, as in the long run I am considering to replace umzug with custom implementation (since it is not doing much...
I won't be releasing any new versions in the 5.x branch, definitely not a feature release, maybe some security fixes. For v5 I would just use the `umzug` property directly...
> 6.2.9 This is quite dated, v6.3 on its own was a really huge release with a lots of fixes in the entity generator, so please try upgrading first (generally...
I will have a closer look later, but one thing I can say right ahead: the `entities` and `entitiesTs` needs to match, you can mix paths and references, but in...
> And both schemas were imported in the module using MikroORMModule.forFeature([customBaseEntitySchema, userSchema]) This is your problem, base entities don't exist on runtime, you cannot call `forFeature` on those. The `forFeature`...
Sure, I will take a closer look at the repro when I have a moment, let's reopen then.
https://github.com/mikro-orm/nestjs/pull/151#issuecomment-2119305771
Sounds good (and simple enough), I guess the first step is allowing to append to the UA from inside the client. Better to do this sooner than later, right?
So it actually looks like the axios upgrade I did some time ago broke the custom UA completely, we didn't have any tests for this. It only works when I...