Add explicit uuid support to forms schema to enable deterministic create/upate behavior across systems#312
Open
makombe wants to merge 1 commit intomekomsolutions:mainfrom
Open
Add explicit uuid support to forms schema to enable deterministic create/upate behavior across systems#312makombe wants to merge 1 commit intomekomsolutions:mainfrom
makombe wants to merge 1 commit intomekomsolutions:mainfrom
Conversation
…ate behavior across systems
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
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.
This PR introduces a required uuid property in the form JSON schema to support deterministic form creation and updates.
Previously, forms could be created with randomly generated UUIDs, which caused inconsistencies across distributed systems and made it difficult to reliably identify and update the same form across different implementations.
With this change: