Asmir Mustafic

let me rephrase your ask. you would like to specify explicitly the migrations, to be able to run the diff command, but to avoid loading the migrations found in the...

What is your goal? You would like ci to fail in that case or what?

Do you have multiple entity managers or did you define the connection or entity manager in your configuration files?

@omarboussarsar @allD245 can you share the doctrine migrations configs that you are using?

@allD245 `doctrine:migrations:diff` needs the entity manager to be able to generate the ORM schema diff. I think that your config file should be: ```yaml doctrine_migrations: storage: table_storage: table_name: migration_versions migrations_paths:...

@omarboussarsar your migrations config file should be ```yaml doctrine_migrations: em: default ``` (or even just omit the em/connection parameter) The admin connection should be used only for production i guess,...

solved in https://github.com/schmittjoh/serializer/pull/1432

I think that this implementation is too much opinionated. Pagination has always been a tricky topic. - `pagination[limit]=1&pagination[offset]=2` - `limit=1&offset=2'` - `page=1&size=100'` - `page=1'` - The `Range` header - whatever......

I would keep yaml. In our projects, fixtures are written by non php-devs, often with minimal dev experience. forcing them to learn PHP is a no go for us...

You can use areas (for the endpoints)