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

Third level is not reactive when update top level parent #88

Closed
johngonzalez opened this issue Jul 23, 2016 · 5 comments
Closed

Third level is not reactive when update top level parent #88

johngonzalez opened this issue Jul 23, 2016 · 5 comments
Labels

Comments

@johngonzalez
Copy link

johngonzalez commented Jul 23, 2016

Congratulations for the package. I have the following pattern:

{
    find: function() {
        // Return a cursor containing top level documents
    },
    children: [
        {
            find: function(topLevelDocument) {
                // Return a cursor of second tier documents.
            },
            children: [ // Third level
                {
                    find: function(secondTierDocument, topLevelDocument) {
                        // Return a cursor of third tier documents. 
                        // But when change some property of topLevelDocument is not reactive
                    },
                    children: [
                       // Repeat as many levels deep as you like
                    ]
                }
            ]
        },
        {
            find: function(topLevelDocument) {
                // Return another cursor of second tier documents.
            }
        }
    ]
}

At third level, is possible get all parent documents as secondTierDocument and topLevelDocument, but when topLevelDocument change, the result isn't update reactively in Third level. I don't know if I am losing some thing or this could a enhancement of this excellent pakage. Thanks

@johngonzalez johngonzalez changed the title Third level is not reactive when change top parent Third level is not reactive when update top level parent Jul 23, 2016
@Nisthar
Copy link

Nisthar commented Feb 22, 2017

@johngonzalez Any solution for this?

@zimme
Copy link
Member

zimme commented May 8, 2017

Please check if this works as expected with the latest version. I believe this might be related to an issue that was fixed in that version.

@jmdsg
Copy link

jmdsg commented Aug 20, 2020

I don't think this issue is solved yet, and i'm using the last version 1.7.3.

@srikant-lavu
Copy link

I'm using version 1.7.3 and having the same issue as @jmdsg

Any update on this? or anyone found a workaround?

Thank you.

@StorytellerCZ
Copy link
Member

Closing and continuing tracking in #146

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

6 participants