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

feat: some field type should have a default value #3753

Closed
magrinj opened this issue Feb 1, 2024 · 0 comments · Fixed by #3991
Closed

feat: some field type should have a default value #3753

magrinj opened this issue Feb 1, 2024 · 0 comments · Fixed by #3991
Assignees
Labels
scope: backend Issues that are affecting the backend side only

Comments

@magrinj
Copy link
Member

magrinj commented Feb 1, 2024

Scope & Context

Field type like TEXT should have a default value of empty string instead of null.

Current behavior

If we don't have a default value provided, this one is set to null.

Expected behavior

Some field type should have a default value instead of null.
By example TEXT should have the default value "".

Technical inputs

This is only applying to the FieldMetadata.

@magrinj magrinj self-assigned this Feb 1, 2024
@magrinj magrinj moved this from 🆕 New to 🔖 Planned in 🎯 Roadmap & Sprints Feb 1, 2024
@magrinj magrinj added the scope: backend Issues that are affecting the backend side only label Feb 2, 2024
@magrinj magrinj moved this from 🔖 Planned to 🏗 In progress in 🎯 Roadmap & Sprints Feb 15, 2024
@magrinj magrinj moved this from 🏗 In progress to 👀 In review in 🎯 Roadmap & Sprints Feb 15, 2024
@github-project-automation github-project-automation bot moved this from 👀 In review to ✅ Done in 🎯 Roadmap & Sprints Feb 16, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
scope: backend Issues that are affecting the backend side only
Projects
Archived in project
Development

Successfully merging a pull request may close this issue.

1 participant