Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Shouldn't it be DoctrineSetList::DOCTRINE_ORM_219? #306

Closed
mvhirsch opened this issue Apr 9, 2024 · 6 comments
Closed

Shouldn't it be DoctrineSetList::DOCTRINE_ORM_219? #306

mvhirsch opened this issue Apr 9, 2024 · 6 comments

Comments

@mvhirsch
Copy link

mvhirsch commented Apr 9, 2024

As the Lexer::* consts got deprecated in v2.19 and the current naming scheme in DoctrineSetList would suggest using _219 (as _214 exists for 2.14).

Shouldn't this be renamed then? https://github.com/rectorphp/rector-doctrine/blob/b3da143634de79b24a266afc07401cfe75a2c49c/config/sets/doctrine-orm-29.php

@JohJohan
Copy link
Contributor

JohJohan commented Mar 5, 2025

@mvhirsch i agree to be consistent in naming it should be _219

@samsonasik is this something we can do as this would be a breaking change

@TomasVotruba
Copy link
Member

TomasVotruba commented Mar 5, 2025

When was the TokenType added? We don't always wait for deprecations (as sometimes they come much later and in different context), but use new features once introduced.

@JohJohan
Copy link
Contributor

JohJohan commented Mar 5, 2025

@TomasVotruba it was added in 2.19 see: doctrine/orm@5049b61.

I think what @mvhirsch was trying to mention is that our file is called doctrine-orm-29.php: https://github.com/rectorphp/rector-doctrine/blob/b3da143634de79b24a266afc07401cfe75a2c49c/config/sets/doctrine-orm-29.php while it should be named doctrine-orm-219.php as it is for version 2.19 and changing that would be a breaking change

@TomasVotruba
Copy link
Member

I see.
The old constant can be kept and only deprecated, not BC change.
Can you add it?

@JohJohan
Copy link
Contributor

JohJohan commented Mar 5, 2025

Yes will do!

@mvhirsch
Copy link
Author

mvhirsch commented Mar 5, 2025

Thank you @JohJohan , @TomasVotruba

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants