Martin Adámek
Martin Adámek
I did a quick and dirty hotfix by awaiting the `useFactory`, which should fix the try/catch block. Keeping this open till we find a proper way. Available in v5.1.6
Closing as resolved via #166, will be part of v5.2.4
> If the config path is automatically inferred from a CLI argument during MikroORM.init(), a deprecation warning is logged. I am still not sure about this one, can you remind...
Ok, thanks for the write-up, agreed with the points you made. > remove empty init altogether I am not so sure about this one, mainly because of the use case...
please don't rebase once you get a review, i have no idea what is changing now
Btw I wanted to ship v6.4 later this week unless you have some plans to PR something worth including in a feature release?
> Considering it's not a breaking change, and the modifications will be to "internal" classes, I think it's ok to have it even in a minor release like 6.4.1 or...
> ok, made deprecated be outputted by default by the default logger... by changing the default of "debugMode" from "false" to "['deprecated']". An explicit "false" would still behave the same...
Indeed, I said we need a way to opt-out. I just don't think we should mix this with the existing mechanism, as deprecations are important and they could be easily...
One last thing is the docs for the `ignoreDeprecations` option, not sure where it fits better, either https://mikro-orm.io/docs/logging or https://mikro-orm.io/docs/configuration (or both)