-
Notifications
You must be signed in to change notification settings - Fork 66
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
A module should let the core know if it supports categorization and on which Doctrine Entities #411
Milestone
Comments
a very good idea. +1 I wonder if there might be a way to generate the information based on scanning the entities? |
This would be a good usecase for module capabilities (defined in Version). Meta data can be stored in there too...
Just a thought. It's not something we need to deal with right at this point as there is a LOT of other structural stuff to do meantime. |
craigh
added a commit
that referenced
this issue
Jun 22, 2015
…ion and for which entities it supports. refs #411. This implements a key in the `capabilities` module as described in the ticket (using American spelling - categorizable). the value for the key is an array of FQ Entity names.
craigh
added a commit
that referenced
this issue
Jun 23, 2015
…ion and for which entities it supports. refs #411. This implements a key in the `capabilities` module as described in the ticket (using American spelling - categorizable). the value for the key is an array of FQ Entity names.
craigh
added a commit
that referenced
this issue
Jun 23, 2015
…ion and for which entities it supports. refs #411. This implements a key in the `capabilities` module as described in the ticket (using American spelling - categorizable). the value for the key is an array of FQ Entity names.
craigh
added a commit
that referenced
this issue
Jun 25, 2015
…ion and for which entities it supports. refs #411. This implements a key in the `capabilities` module as described in the ticket (using American spelling - categorizable). the value for the key is an array of FQ Entity names.
craigh
added a commit
that referenced
this issue
Jun 30, 2015
…ion and for which entities it supports. refs #411. This implements a key in the `capabilities` module as described in the ticket (using American spelling - categorizable). the value for the key is an array of FQ Entity names.
craigh
added a commit
that referenced
this issue
Jul 2, 2015
…ion and for which entities it supports. refs #411. This implements a key in the `capabilities` module as described in the ticket (using American spelling - categorizable). the value for the key is an array of FQ Entity names.
craigh
added a commit
that referenced
this issue
Jul 9, 2015
…ion and for which entities it supports. refs #411. This implements a key in the `capabilities` module as described in the ticket (using American spelling - categorizable). the value for the key is an array of FQ Entity names.
craigh
added a commit
that referenced
this issue
Jul 18, 2015
…ion and for which entities it supports. refs #411. This implements a key in the `capabilities` module as described in the ticket (using American spelling - categorizable). the value for the key is an array of FQ Entity names.
craigh
added a commit
that referenced
this issue
Jul 19, 2015
…ion and for which entities it supports. refs #411. This implements a key in the `capabilities` module as described in the ticket (using American spelling - categorizable). the value for the key is an array of FQ Entity names.
craigh
added a commit
that referenced
this issue
Jul 24, 2015
…ion and for which entities it supports. refs #411. This implements a key in the `capabilities` module as described in the ticket (using American spelling - categorizable). the value for the key is an array of FQ Entity names.
craigh
added a commit
that referenced
this issue
Jul 25, 2015
…ion and for which entities it supports. refs #411. This implements a key in the `capabilities` module as described in the ticket (using American spelling - categorizable). the value for the key is an array of FQ Entity names.
craigh
added a commit
that referenced
this issue
Jul 28, 2015
…ion and for which entities it supports. refs #411. This implements a key in the `capabilities` module as described in the ticket (using American spelling - categorizable). the value for the key is an array of FQ Entity names.
craigh
added a commit
that referenced
this issue
Jul 30, 2015
…ion and for which entities it supports. refs #411. This implements a key in the `capabilities` module as described in the ticket (using American spelling - categorizable). the value for the key is an array of FQ Entity names.
craigh
added a commit
that referenced
this issue
Aug 11, 2015
…ion and for which entities it supports. refs #411. This implements a key in the `capabilities` module as described in the ticket (using American spelling - categorizable). the value for the key is an array of FQ Entity names.
I believe this was complete in Core-1.4.0 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
During the Categories refactoring to Doctrine 2, i came upon some issues regarding Category registry that need to be dealt with in the future.
First of all, not all modules support categorization, but in Category registry -> Choose module, the user can see all the installed modules. This is bad usability. So in order to solve this, a module should let the core know if indeed it supports categorization. If it does, it will be listed inside the select box. If it doesn't, it will not.
Second, not all entities of the module support categorization, but in Category registry -> Choose entity, the user can see all entities of the module. bad usability again. The module should let the core know, which of it's entities support categorization. If they do, they will be listed inside the select box.
The text was updated successfully, but these errors were encountered: