Annotations 2.0: Read annotations from functions#1
Annotations 2.0: Read annotations from functions#1FabioBatSilva merged 5 commits intoFabioBatSilva:2.0from
Conversation
|
Tried my best to get better coveralls ratings. Happy about feedback when testing the |
|
@guilhermeblanco @FabioBatSilva Any news on this? |
|
@lennerd I'll revisit this branch as soon as start on the ClassMetadata dump support on ORM. |
|
Whats the status here? |
|
Currently Having I would suggest something like : |
|
@FabioBatSilva Thanks for the feedback! I'm a little confused however. class AnnotationReader implements FunctionalReader, ObjectReader {}
class CachedReader implements FunctionalReader, ObjectReader {}Isn't that a little contrary to the following?
And why would you not have the |
|
That is correct I think we need to either segregate the implementations for Single implementation:interface Reader extends FunctionalReader, ObjectReader {}
class AnnotationReader implements Reader {}
class CachedReader implements Reader
{
/** @var \Doctrine\Annotations\Reader */
private $delegate;
}Split implementations:class FunctionalAnnotationReader implements FunctionalReader {}
class ObjectAnnotationReader implements ObjectReader {}
class CachedFunctionalReader implements FunctionalReader {}
class CachedObjectReader implements FunctionalReader {} |
|
Ah I see what you mean. I think I like the first approach to be much simpler and more compliant with the current implementation. Will try this and come back to you. |
|
I just added the single implementation approach you were describing. Thanks again for the feedback. Quite happy with the simplifications in the Again I would be happy about any kind of thoughts and feedback. |
|
@FabioBatSilva @guilhermeblanco Any more feedback? |
|
Nearly a year ago we started this. Any news or plans? Just looked through the code and I'm really impressed by the many improvements you added (especially the hoa parser) and how easy it was for me to add annotations for functions. 😕 |
|
Hi @lennerd .. Thanks for your work here and sorry for the looooong delay.. I'm not sure when 2.0 is going to happen. |
|
Hey @FlavioBatSilva,
if you agree with all changes, that would be great! 😉 Great to see that the work for 2.0 is starting again! 👍 |
|
@FabioBatSilva WHY U NO MERGE THEN? PS: In your own fork, I'm sayin'... |
|
😄 |
|
My Bad.. 😜 Thanks @lennerd ! |
I know, this is maybe a strange way to add this functionality, but as this changes should be on top of doctrine#75 I think it's best to make this PR agains this forked repository to be able to focus on the right changes.
Mind that this is also a very big WIP in the title, as I really need to see what are the Do's and Dont's in the doctrine family. I'm really happy to hear, what you think and open to every kind of feedback.
Fixes: doctrine#83 (comment)