Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Potential solution to handling arrays #2565

Draft
wants to merge 1 commit into
base: main
Choose a base branch
from

Conversation

sdwolfz
Copy link
Contributor

@sdwolfz sdwolfz commented Apr 4, 2024

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?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant