Initially, the term "annotations" was used due to the lack of native PHP support for meta annotations over methods and properties.
After PHP 7, PHP introduced attributes - a native instrument available via PHP reflection to add meta information.
GraphQLite dropped support for Doctrine annotations after #677 (GraphQLite 7)
What about changing naming used everywhere - use attribute instead of annotation?
Examples:
|
/** |
|
* A marker interface for annotations meant to be used in middlewares |
|
*/ |
|
interface MiddlewareAnnotationInterface |
|
namespace TheCodingMachine\GraphQLite\Annotations; |
Initially, the term "annotations" was used due to the lack of native PHP support for meta annotations over methods and properties.
After PHP 7, PHP introduced attributes - a native instrument available via PHP reflection to add meta information.
GraphQLite dropped support for Doctrine annotations after #677 (GraphQLite 7)
What about changing naming used everywhere - use
attributeinstead ofannotation?Examples:
graphqlite/src/Annotations/MiddlewareAnnotationInterface.php
Lines 7 to 10 in 5403473
graphqlite/src/Annotations/Cost.php
Line 5 in 5403473