You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Feb 6, 2020. It is now read-only.
As I was researching generate-factory-for-class today to create a tutorial on it, I noticed that while most classes referenced in the factory classes it generates were relative, with their fully qualified namespaces included via use statements, classes which were pulled from the container were not.
I'm not sure if there's something that I've missed; but to me, for consistency's sake if nothing else, it makes sense to have classes retrieved from the container be relative as well.
The text was updated successfully, but these errors were encountered:
fwiw, great job on the class. The generated classes are excellently formatted, with proper docblock comments, etc. Thanks for making this happen.
settermjd
changed the title
Factories created by generate-factory-for-class specify a fully-qualified namespace for classes pulled from the container
Factories created by generate-factory-for-class have fully-qualified namespace for classes pulled from the container
Jan 13, 2017
@weierophinney, here is the issue, as requested.
As I was researching
generate-factory-for-class
today to create a tutorial on it, I noticed that while most classes referenced in the factory classes it generates were relative, with their fully qualified namespaces included viause
statements, classes which were pulled from the container were not.Here's an example of what I mean:
I'm not sure if there's something that I've missed; but to me, for consistency's sake if nothing else, it makes sense to have classes retrieved from the container be relative as well.
The text was updated successfully, but these errors were encountered: