Bob van de Vijver

This seems to be fully resolved :+1:

I got about 200 deprecation notices in a single project because of the deprecation of the `Criteria::ASC` / `Criteria::DESC`, and while migrating to `Order::Ascending->value` might be an option, I do...

@jasonlundien Thank you for your effort! I just checked my project, and I can no longer reproduce this issue at all. I'm not even seeing the warning you mention in...

It looks like that reverting to the non-rust consumers has fixed it for now: I haven't seen the offset issue return since when I created the ticket and removed the...

~~Note that I did not add the `--no-strict-offset-reset` option, I only switched to the non-rust consumers. And the error hasn't returned since for us.~~ Update June 4th: The error did...

I believe this indeed solves an issue with automapping, but I am not really charmed that some automapping logic is still being executed when explicitly disabled. There is no convenient...

> Actually it's not. There's a "disabled" option if you really want to disable any mapping. Disabling any mapping is on a complete other level than disabling the auto mapping...

> There is to me: either provide an explicit mapping, or use disabled: true. > > there must be an explicit mapping in existing apps when this is used today...

> yep, this will indeed behave differently if the only outcome you wanted from this mapping was to disable entity-mapping altogether. No, this will behave differently if the only outcome...

> Well, we circle back to [#54455 (comment)](https://github.com/symfony/symfony/pull/54455#issuecomment-2046855506): if you disabled automapping by default, then you must have added explicit mappings. And if you added an attribute with `mapping: []`...