javaDeveloperKid

> Feel free to explore this issue and maybe send a PR. I'll be happy to take a look at it. Hmmm, this feature look encouragingly. It would also be...

Yes but that breaks the code. I've always thought that Rector supports instant upgrades without breaking a code. However if you claim this is not a bug and Rector can't/shouldn't...

Yes, I do get HTTP 500 with the error "Unknown named parameter $name". https://github.com/sensiolabs/SensioFrameworkExtraBundle/blob/v6.1.5/src/Configuration/ParamConverter.php

It can't. It works for annotations because this is how annotations work with public properties. But migrating from annotations to attributes results in the problem described here because attributes use...

I can't really say. I reported issue about ParamConverter because I encountered this in my project. The question is whether Rector can/should support this. AnnotationToAttributeRetctor is a generic rector and...

I would measure the work needed for both scenarios and then pick the optimal one. Everyone understands that opensource maintainers have a lot of work so "my" issue is not...

> a warning in console could be very helpful. and would show a user that Rector is aware of it's current limitation and people would not treat this as a...

Thank you @Chris53897 for reporting this issue. I can see rector did the same error in my app that I'm migrating right now.

Hi, For me the `--cache` option reduces build time significantly. However I agree that we should be able to enable base image caching separately from layers caching.

You can write your own serializer that will fill Amazon requirements