Skip to content
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

@ManyToMany association: handling displaying field from a related entity for both entities #43

Closed
max-dev opened this issue Feb 17, 2013 · 1 comment
Assignees
Milestone

Comments

@max-dev
Copy link
Member

max-dev commented Feb 17, 2013

Steps to reproduce:

  1. Configure ManyToMany relationship between two entities
  2. Enable AdministrationConfiguration for both of them, having added the @manytomany field to ListView as field (not renderable)
  3. Navigate to ListView/FormView of [Entity1]/[Entity2]

see example in Customer <=> DiscountProgram [CustomerAdministration/DiscountProgramAdministration]
or test ManyToManyField.canBeShownOnListView()

@ghost ghost assigned aliubunia Feb 17, 2013
ikostenko added a commit that referenced this issue Feb 17, 2013
@max-dev
Copy link
Member Author

max-dev commented Feb 19, 2013

To reproduce this, we need have ManyToMany relation from both sides to be configured in AdministrationConfiguration.
Json serialization process falls into recursion trying to serialize back reference.
Question to @ikostenko: Actually I'm not sure it's critical, usually we add links just from one side.

@ghost ghost assigned max-dev and ikostenko Feb 19, 2013
ikostenko added a commit that referenced this issue Feb 21, 2013
@ghost ghost assigned max-dev Feb 21, 2013
max-dev added a commit that referenced this issue Mar 3, 2013
max-dev added a commit that referenced this issue Mar 3, 2013
@ghost ghost assigned ikostenko Mar 4, 2013
@max-dev max-dev closed this as completed Mar 4, 2013
ikostenko added a commit that referenced this issue Mar 4, 2013
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants