doctrine/archived-orm
1
0
Fork 0
mirror of https://github.com/doctrine/orm.git synced 2026-03-23 22:42:18 +01:00
Code Issues 5.3k Packages Projects Releases 100 Wiki Activity

DDC-1198: Add PHPDocs to annotationclasses #1508

New Issue
Closed
opened 2026-01-22 13:16:28 +01:00 by admin · 1 comment
admin commented 2026-01-22 13:16:28 +01:00
Owner
Copy Link

Originally created by @doctrinebot on GitHub (Jun 8, 2011).

Originally assigned to: @Ocramius on GitHub.

Jira issue originally created by user pulse00:

If an IDE would like to support annotations, it's currently only possible to display all resolvable classes in a code-hint menu when autocompleting annotations, as
basically any class can be used for annotations.

To make it possible for IDEs to detect classes which are explicitly meant to be used as annotations, it would be nice to agree on some common
way of documenting annotations in PHPDocBlocks.

Here's an example of what this could look like:

25a14e9edc

This way IDEs can prioritize annotated classes in code-hints and add additional information to the user.

Originally created by @doctrinebot on GitHub (Jun 8, 2011). Originally assigned to: @Ocramius on GitHub. Jira issue originally created by user pulse00: If an IDE would like to support annotations, it's currently only possible to display all resolvable classes in a code-hint menu when autocompleting annotations, as basically any class can be used for annotations. To make it possible for IDEs to detect classes which are explicitly meant to be used as annotations, it would be nice to agree on some common way of documenting annotations in PHPDocBlocks. Here's an example of what this could look like: https://github.com/pulse00/doctrine2/commit/25a14e9edc406edfd33e54fc38922a191e9cbe83 This way IDEs can prioritize annotated classes in code-hints and add additional information to the user.
admin added the ImprovementInvalid labels 2026-01-22 13:16:28 +01:00
admin closed this issue 2026-01-22 13:16:30 +01:00
admin commented 2026-01-22 13:16:30 +01:00
Author
Owner
Copy Link

@malukenho commented on GitHub (Jan 3, 2017):

@Ocramius @lcobucci It's not related to the ORM IMHO

@malukenho commented on GitHub (Jan 3, 2017): @Ocramius @lcobucci It's not related to the ORM IMHO
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
BC Break
Bug
Can't Fix
Deprecation
Documentation
DQL
Duplicate
Failing Test
Hacktoberfest
Improvement
Improvement
Incomplete
Invalid
Missing Tests
New Feature
PR Created
pull-request
Mirrored from GitHub Pull Request
 Question
Regression
Status: Waiting feedback
Waiting feedback
WIP
Won't Fix
No Label Improvement Invalid
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
admin
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: doctrine/archived-orm#1508
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?