Potential solution to handling arrays #2565
Draft
Conversation
This file contains 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.
Before I proceed with this further I need to know if this is the right approach, and also I'd like advice on how to handle errors in cases like this.
This has the potential to be a big change reason why I just showcase a small sample.
The idea is: if we have an array column we should treat it as a string containing JSON data that people can edit as is. It's the simplest thing I could think of.
Right now, if you have an array column in the DB, the value is neither displayed nor saved correctly in the form, which leads to corrupting the data if the form is submitted with that field.
What do you think? Is this approach OK? Should I continue with this for other fields types?