Don't define Doctrine annotations as a hard dependency? #6769

Closed
opened 2026-01-22 15:38:17 +01:00 by admin · 1 comment
Owner

Originally created by @javiereguiluz on GitHub (Jun 25, 2021).

In #8266 @beberlei added support for defining mapping with PHP attributes. However, doctrine/annotations is still defined as a required dependency of this project:

f233e4cf6b/composer.json (L22)

Is there any technical reason to keep it as is, or is it just that we need to find someone willing to contribute this change? Thanks!

Originally created by @javiereguiluz on GitHub (Jun 25, 2021). In #8266 @beberlei added support for defining mapping with PHP attributes. However, `doctrine/annotations` is still defined as a required dependency of this project: https://github.com/doctrine/orm/blob/f233e4cf6b62a90a9d3ce5c5cad055dce944ce7c/composer.json#L22 Is there any technical reason to keep it as is, or is it just that we need to find someone willing to contribute this change? Thanks!
admin closed this issue 2026-01-22 15:38:18 +01:00
Author
Owner

@alcaeus commented on GitHub (Jun 25, 2021):

There is no hard requirement with attributes, and there shouldn't have been one in the first place. I believe a solution as implemented in doctrine/persistence#197 would make sense here.

@alcaeus commented on GitHub (Jun 25, 2021): There is no hard requirement with attributes, and there shouldn't have been one in the first place. I believe a solution as implemented in doctrine/persistence#197 would make sense here.
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: doctrine/archived-orm#6769