You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The main reason I ask is that js ecosystem is based on json and most tooling talks json.
Compelling as it may be committing to only use homebase entities without a very easy way back is too high of a price to pay.
I realise that the relations makes it a bit hard to "know where to stop" then I'm guessing query language is probably the right answer here, something like datomic/datascript q/pull would probably do the trick.
Loved the project (homebase-react & homebase) BTW, and I'm working on a POC that, if successful, might evolve to a large scale production use in our company.
The text was updated successfully, but these errors were encountered:
Hey @lidorcg. JSON support is certainly on the roadmap although probably not for the entity API. We're focusing more on the query and pull APIs going forward. Entity is great, but it has a bit too much magic and getting all that magic to work across the whole local-first pipeline was too heavy of a lift for the MVP we're working on.
Here's more info about why exporting JSON is difficult #97 (comment)
The next release of homebase-react will make fewer assumptions so it will have a slightly steeper learning curve, but converting from EDN -> JSON and back again will be much less complicated.
The main reason I ask is that js ecosystem is based on json and most tooling talks json.
Compelling as it may be committing to only use homebase entities without a very easy way back is too high of a price to pay.
I realise that the relations makes it a bit hard to "know where to stop" then I'm guessing query language is probably the right answer here, something like datomic/datascript q/pull would probably do the trick.
Loved the project (homebase-react & homebase) BTW, and I'm working on a POC that, if successful, might evolve to a large scale production use in our company.
The text was updated successfully, but these errors were encountered: