-
Notifications
You must be signed in to change notification settings - Fork 55
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
ngRestRelations displays records only from first pool #454
Comments
could you please post your config/models and the sub relation your are talking about? so i can clearly see what your configuration is and i can try to reproduce. |
@nadar here I created minimal config to show it tables
in module
Bar model
Foo model
If you will create records in both Foo pools for the same parent Bar record and then will choose relation 'Foo' in parent Bar record, it will list not all child records but only Foo records from Pool1. |
So i would say the expected result is that
should list all items for this model? Wether they are in a certain pool or not. |
@nadar yeah, in current form, as we configure It can be a feature if we can also configure a pool as a data provider, but we should be able to choose which pool to use, not just first encountered as it is currently. Or be able not to use any pool but show all records. In my case the records go between pools as they being processed so they suddenly appear and disappear from the relation list :) PS also addition to the bug: if you open Bar-Foo relation and choose to create new Foo record, then it is being created in first pool only, you can't choose 'type'=2 in above example, as the field not displayed. |
Maybe a similar cause as in #455 - missing second parameter |
What steps will reproduce the problem?
ngRestRelations used for linked records which have several ngRestPools
What is the expected result?
all child records being shown in list view
What do you get instead? (A Screenshot can help us a lot!)
list with child records only from first pool (which goes first in menu)
The text was updated successfully, but these errors were encountered: