The problem is that when you have a deep data graph: <div class="snippet-clipboard

API candidate: <div class="snippet-clipboard-content notranslate position-relative

Conditional Reactivity Graph about grapher HOT 2 CLOSED

theodorDiaconu commented on June 1, 2024

Conditional Reactivity Graph

from grapher.

Comments (2)

theodorDiaconu commented on June 1, 2024

API candidate:

const query = createQuery {
  users: {
     posts: {
         comments: {
          }
     }
  }
}

Sentient Query (naming can be changed, but we need a badass name for this 😄 )

const sentientQuery = new SentientQuery(query, {
   users: {
       _id: 1, // by enabling reactivity only on _id, you have reactivity whether something was added or removed, not necessarily had a field changed.
       posts: {
           // If you don't specify any direct field, no reactivity will be involved at that level.
           isPublished: 1, // when you specify at least one field different from _id, _id will be automatically added, any other field will "listen" to changes
           comments: {
                _id: 1, // only when comment is added, removed
           }
       }
   }
})

So, we use the same "graph" explicity to describe where we want reactivity. Then we would do something like:

sentientQuery.subscribe();
// fetches the data statically, then creates propper subscriptions
// when any of that subscription is changed, it will only fetch it's data and data under it.
sentientQuery.fetch() // retrieves the data from the sentientQuery cache

Make it hellishly performant, we may need the "Hypernova Subscription" for this. Need to think.

from grapher.

theodorDiaconu commented on June 1, 2024

After some analysis I think this is not possible.

from grapher.

Recommend Projects