Discussion:
[doctrine-user] Entity generation directory layout
MetaAbstract
2017-11-04 16:46:56 UTC
Permalink
I generate entities from xml metadata. But namespace for them have several
levels. So all levels of namespace was converted to directory structure
under the target directory for generation. But in the namespace in head are
several abstract levels like brand and project, may be module. From other
side composer autoloader exist and give possibility to map directories and
namespaces for autolading.

Is it possible to control this behavior during generation? For example
generate php classes directly in target dir or cut some head namespace from
full namespace of entity before create directory structure?
--
You received this message because you are subscribed to the Google Groups "doctrine-user" group.
To unsubscribe from this group and stop receiving emails from it, send an email to doctrine-user+***@googlegroups.com.
To post to this group, send email to doctrine-***@googlegroups.com.
Visit this group at https://groups.google.com/group/doctrine-user.
For more options, visit https://groups.google.com/d/optout.
Marco Pivetta
2017-11-04 16:51:22 UTC
Permalink
The entities are always generated in a PSR-0 (*not* PSR-4) compliant
structure given a root directory.

Marco Pivetta

http://twitter.com/Ocramius

http://ocramius.github.com/
Post by MetaAbstract
I generate entities from xml metadata. But namespace for them have several
levels. So all levels of namespace was converted to directory structure
under the target directory for generation. But in the namespace in head are
several abstract levels like brand and project, may be module. From other
side composer autoloader exist and give possibility to map directories and
namespaces for autolading.
Is it possible to control this behavior during generation? For example
generate php classes directly in target dir or cut some head namespace from
full namespace of entity before create directory structure?
--
You received this message because you are subscribed to the Google Groups
"doctrine-user" group.
To unsubscribe from this group and stop receiving emails from it, send an
Visit this group at https://groups.google.com/group/doctrine-user.
For more options, visit https://groups.google.com/d/optout.
--
You received this message because you are subscribed to the Google Groups "doctrine-user" group.
To unsubscribe from this group and stop receiving emails from it, send an email to doctrine-user+***@googlegroups.com.
To post to this group, send email to doctrine-***@googlegroups.com.
Visit this group at https://groups.google.com/group/doctrine-user.
For more options, visit https://groups.google.com/d/optout.
Артем Мельчук
2017-11-04 17:47:35 UTC
Permalink
ok. thx. Will try to hack it.

С УважеМОеЌ, Мельчук АртеЌ.
Post by Marco Pivetta
The entities are always generated in a PSR-0 (*not* PSR-4) compliant
structure given a root directory.
Marco Pivetta
http://twitter.com/Ocramius
http://ocramius.github.com/
Post by MetaAbstract
I generate entities from xml metadata. But namespace for them have
several levels. So all levels of namespace was converted to directory
structure under the target directory for generation. But in the namespace
in head are several abstract levels like brand and project, may be module.
From other side composer autoloader exist and give possibility to map
directories and namespaces for autolading.
Is it possible to control this behavior during generation? For example
generate php classes directly in target dir or cut some head namespace from
full namespace of entity before create directory structure?
--
You received this message because you are subscribed to the Google Groups
"doctrine-user" group.
To unsubscribe from this group and stop receiving emails from it, send an
Visit this group at https://groups.google.com/group/doctrine-user.
For more options, visit https://groups.google.com/d/optout.
--
You received this message because you are subscribed to a topic in the
Google Groups "doctrine-user" group.
To unsubscribe from this topic, visit https://groups.google.com/d/
topic/doctrine-user/O1Gi3DZ0iek/unsubscribe.
To unsubscribe from this group and all its topics, send an email to
Visit this group at https://groups.google.com/group/doctrine-user.
For more options, visit https://groups.google.com/d/optout.
--
You received this message because you are subscribed to the Google Groups "doctrine-user" group.
To unsubscribe from this group and stop receiving emails from it, send an email to doctrine-user+***@googlegroups.com.
To post to this group, send email to doctrine-***@googlegroups.com.
Visit this group at https://groups.google.com/group/doctrine-user.
For more options, visit https://groups.google.com/d/optout.
Marco Pivetta
2017-11-04 17:56:33 UTC
Permalink
It's not supposed to be hacked - it is intended behavior. If you need the
generated files to be moved somewhere else, you will need to do so yourself

Marco Pivetta

http://twitter.com/Ocramius

http://ocramius.github.com/
Post by Артем Мельчук
ok. thx. Will try to hack it.
С УважеМОеЌ, Мельчук АртеЌ.
Post by Marco Pivetta
The entities are always generated in a PSR-0 (*not* PSR-4) compliant
structure given a root directory.
Marco Pivetta
http://twitter.com/Ocramius
http://ocramius.github.com/
Post by MetaAbstract
I generate entities from xml metadata. But namespace for them have
several levels. So all levels of namespace was converted to directory
structure under the target directory for generation. But in the namespace
in head are several abstract levels like brand and project, may be module.
From other side composer autoloader exist and give possibility to map
directories and namespaces for autolading.
Is it possible to control this behavior during generation? For example
generate php classes directly in target dir or cut some head namespace from
full namespace of entity before create directory structure?
--
You received this message because you are subscribed to the Google
Groups "doctrine-user" group.
To unsubscribe from this group and stop receiving emails from it, send
Visit this group at https://groups.google.com/group/doctrine-user.
For more options, visit https://groups.google.com/d/optout.
--
You received this message because you are subscribed to a topic in the
Google Groups "doctrine-user" group.
To unsubscribe from this topic, visit https://groups.google.com/d/to
pic/doctrine-user/O1Gi3DZ0iek/unsubscribe.
To unsubscribe from this group and all its topics, send an email to
Visit this group at https://groups.google.com/group/doctrine-user.
For more options, visit https://groups.google.com/d/optout.
--
You received this message because you are subscribed to the Google Groups
"doctrine-user" group.
To unsubscribe from this group and stop receiving emails from it, send an
Visit this group at https://groups.google.com/group/doctrine-user.
For more options, visit https://groups.google.com/d/optout.
--
You received this message because you are subscribed to the Google Groups "doctrine-user" group.
To unsubscribe from this group and stop receiving emails from it, send an email to doctrine-user+***@googlegroups.com.
To post to this group, send email to doctrine-***@googlegroups.com.
Visit this group at https://groups.google.com/group/doctrine-user.
For more options, visit https://groups.google.com/d/optout.
Артем Мельчук
2017-11-05 11:17:50 UTC
Permalink
it's ok. I just going to use symlinks for path substitution. Will hack
system outside till PSR-4.

С УважеМОеЌ, Мельчук АртеЌ.
Post by Marco Pivetta
It's not supposed to be hacked - it is intended behavior. If you need the
generated files to be moved somewhere else, you will need to do so yourself
Marco Pivetta
http://twitter.com/Ocramius
http://ocramius.github.com/
Post by Артем Мельчук
ok. thx. Will try to hack it.
С УважеМОеЌ, Мельчук АртеЌ.
Post by Marco Pivetta
The entities are always generated in a PSR-0 (*not* PSR-4) compliant
structure given a root directory.
Marco Pivetta
http://twitter.com/Ocramius
http://ocramius.github.com/
Post by MetaAbstract
I generate entities from xml metadata. But namespace for them have
several levels. So all levels of namespace was converted to directory
structure under the target directory for generation. But in the namespace
in head are several abstract levels like brand and project, may be module.
From other side composer autoloader exist and give possibility to map
directories and namespaces for autolading.
Is it possible to control this behavior during generation? For example
generate php classes directly in target dir or cut some head namespace from
full namespace of entity before create directory structure?
--
You received this message because you are subscribed to the Google
Groups "doctrine-user" group.
To unsubscribe from this group and stop receiving emails from it, send
Visit this group at https://groups.google.com/group/doctrine-user.
For more options, visit https://groups.google.com/d/optout.
--
You received this message because you are subscribed to a topic in the
Google Groups "doctrine-user" group.
To unsubscribe from this topic, visit https://groups.google.com/d/to
pic/doctrine-user/O1Gi3DZ0iek/unsubscribe.
To unsubscribe from this group and all its topics, send an email to
Visit this group at https://groups.google.com/group/doctrine-user.
For more options, visit https://groups.google.com/d/optout.
--
You received this message because you are subscribed to the Google Groups
"doctrine-user" group.
To unsubscribe from this group and stop receiving emails from it, send an
Visit this group at https://groups.google.com/group/doctrine-user.
For more options, visit https://groups.google.com/d/optout.
--
You received this message because you are subscribed to a topic in the
Google Groups "doctrine-user" group.
To unsubscribe from this topic, visit https://groups.google.com/d/
topic/doctrine-user/O1Gi3DZ0iek/unsubscribe.
To unsubscribe from this group and all its topics, send an email to
Visit this group at https://groups.google.com/group/doctrine-user.
For more options, visit https://groups.google.com/d/optout.
--
You received this message because you are subscribed to the Google Groups "doctrine-user" group.
To unsubscribe from this group and stop receiving emails from it, send an email to doctrine-user+***@googlegroups.com.
To post to this group, send email to doctrine-***@googlegroups.com.
Visit this group at https://groups.google.com/group/doctrine-user.
For more options, visit https://groups.google.com/d/optout.
Артем Мельчук
2017-11-05 11:44:20 UTC
Permalink
hacked))))

С УважеМОеЌ, Мельчук АртеЌ.
Post by Артем Мельчук
it's ok. I just going to use symlinks for path substitution. Will hack
system outside till PSR-4.
С УважеМОеЌ, Мельчук АртеЌ.
Post by Marco Pivetta
It's not supposed to be hacked - it is intended behavior. If you need the
generated files to be moved somewhere else, you will need to do so yourself
Marco Pivetta
http://twitter.com/Ocramius
http://ocramius.github.com/
Post by Артем Мельчук
ok. thx. Will try to hack it.
С УважеМОеЌ, Мельчук АртеЌ.
Post by Marco Pivetta
The entities are always generated in a PSR-0 (*not* PSR-4) compliant
structure given a root directory.
Marco Pivetta
http://twitter.com/Ocramius
http://ocramius.github.com/
Post by MetaAbstract
I generate entities from xml metadata. But namespace for them have
several levels. So all levels of namespace was converted to directory
structure under the target directory for generation. But in the namespace
in head are several abstract levels like brand and project, may be module.
From other side composer autoloader exist and give possibility to map
directories and namespaces for autolading.
Is it possible to control this behavior during generation? For example
generate php classes directly in target dir or cut some head namespace from
full namespace of entity before create directory structure?
--
You received this message because you are subscribed to the Google
Groups "doctrine-user" group.
To unsubscribe from this group and stop receiving emails from it, send
Visit this group at https://groups.google.com/group/doctrine-user.
For more options, visit https://groups.google.com/d/optout.
--
You received this message because you are subscribed to a topic in the
Google Groups "doctrine-user" group.
To unsubscribe from this topic, visit https://groups.google.com/d/to
pic/doctrine-user/O1Gi3DZ0iek/unsubscribe.
To unsubscribe from this group and all its topics, send an email to
Visit this group at https://groups.google.com/group/doctrine-user.
For more options, visit https://groups.google.com/d/optout.
--
You received this message because you are subscribed to the Google
Groups "doctrine-user" group.
To unsubscribe from this group and stop receiving emails from it, send
Visit this group at https://groups.google.com/group/doctrine-user.
For more options, visit https://groups.google.com/d/optout.
--
You received this message because you are subscribed to a topic in the
Google Groups "doctrine-user" group.
To unsubscribe from this topic, visit https://groups.google.com/d/to
pic/doctrine-user/O1Gi3DZ0iek/unsubscribe.
To unsubscribe from this group and all its topics, send an email to
Visit this group at https://groups.google.com/group/doctrine-user.
For more options, visit https://groups.google.com/d/optout.
--
You received this message because you are subscribed to the Google Groups "doctrine-user" group.
To unsubscribe from this group and stop receiving emails from it, send an email to doctrine-user+***@googlegroups.com.
To post to this group, send email to doctrine-***@googlegroups.com.
Visit this group at https://groups.google.com/group/doctrine-user.
For more options, visit https://groups.google.com/d/optout.
Loading...