Firebase "symlink" to another node -


in relation other question modelling real user-facing tree structure (using firebase tree structure represent "document outline" structure directly), thinking of putting in place generic approach "symlinking", @ nesting levels, overcome 32 nesting levels limitation , need fetch sub-nodes @ once.

are there "best-practices" "symlinking" in firebase?

e.g.:

  • syntax (contents, key-value structure) firebase node symbolise link node
  • should symlink contain path target node (absolute or relative?) or kind of globally unique id?
  • api callback triggered when symlink content finishes loading asynchronously

i envisioning little wrapper api abstract difference of whether node there or accessed indirectly via "symlink". there api method "now fetch me this/more" user wants more details on displayed data (e.g. drilling down deeper in tree), , fetch e.g. next level of nesting (via callback), abstracting away whether children's content there or symlinked...

does seem idea in general?


Comments

Popular posts from this blog

Listboxes in c# -

Excel Duty List -

Multilayer CSV to filtered excel -