Example 2 - With FaunaDB real-time #13
Draft
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
This pull request is being automatically deployed with Vercel (learn more). 🔍 Inspect: https://vercel.com/ambroise-dhenain/poc-nextjs-reaflow/H3hEAc36vSdwoRgchvvDHAg8wSfL |
Vadorequest
changed the title
…of them is missing (will destroy all existing datasets upon load)
# Conflicts: # src/components/Footer.tsx # src/components/Nav.tsx
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
The canvas dataset is stored in FaunaDB.
Changes to the canvas are real-time and shared with everyone.
Everybody shares the same working document.
This branch is meant to be kept as an example. It is automatically deployed on Vercel, which allows us to have a dedicated deployment for this variant.
Demo: https://poc-nextjs-reaflow-git-with-faunadb-real-time-ambroise-dhenain.vercel.app
Known issues
Concurrent updates: There are a few issues due to concurrent updates overwriting each other (nodes content jumping). This issue has been solved in #12 using a queue of mutations but won't be backported to this example.