The record edition form
I have a field that:
is non-nullable in Postgres
has the empty string as default value ("")
The frontend validators prevent me from submitting the edition form if I don’t set a value.
I would like to be able to submit the form and use the default value (empty string)
In my code I set the following so that the frontend validation leave me submit the form.
Project name: Roundtable
Team name: Operations
Environment name: All
Agent (forest package) name & version: latest agent-nodejs
Database type: postgres
Recent changes made on your end if any: none related, this never worked
1 Like
Hello @Romain_Gilliotte ,
Hope you’re doing well
Out of curiosity, what’s the interest in your case to have set this field as a non-nullable value but to make it equal to empty string when there is no value?
No reason really, other that this is how the records are created by my customer’s public facing application and I can’t change it.
I don’t have access to neither the source code of the public facing app, nor permissions to do any structural change in the database.
vince
January 10, 2024, 10:18am
4
Hey @Romain_Gilliotte
Is it during a creation or an edition?
Hey @Romain_Gilliotte ,
Gotcha!
Well, your use case is pretty special.
Thanks for the feedback.
It is during edition in my case
The issue is that when the user open the form to edit something unrelated, they can’t save because of the frontend validation (the field already contains an empty string and is not modified)
I’m doing great
1 Like
Woops, that’s worst than what I thought.
Thank you Romain and happy new year to you too!
vince
January 17, 2024, 3:58pm
8
Hey @Romain_Gilliotte ,
I tried to reproduce your issue but without success.
I sent your a private message with a link to a screencast
Our setup:
Non-nullable field with default value = “”
Agent nodejs (as the frontend validation rules come from the agent)
Postgres (maybe not the same implementation depending on driver)
Then:
Try to edit any field of the record
It should fail in the frontend (without making a request to the agent) because the “Present” validator which is set on the non nullable field
Hello @Romain_Gilliotte ,
Thanks for your clarification.
I can surely reproduce.
We’re on it anyway!
In this particular collection, the records are not created using the admin panel, but by the customer facing application
So I did not get to actually try creating a new record (the role configuration on forestadmin forbids it).
Still, I’m pretty sure that the issue is the same for creation / edition.
anon34731316:
We’re on it anyway!
Thanks a lot!
It’s just strange.
filterOperators,
type: 'Column',
validation: [],
isReadOnly: attribute.autoIncrement,
isSortable: true,
};
if (
attribute.allowNull === false &&
!column.isReadOnly &&
!attribute.defaultValue &&
// eslint-disable-next-line no-underscore-dangle
!attribute._autoGenerated
) {
column.validation.push({ operator: 'Present' });
}
if (attribute.primaryKey) column.isPrimaryKey = true;
if (
attribute.defaultValue !== null &&
Hello Romain,
A fix has just been released (on the frontend repository actually).
Thanks
I’m still seeing the little * next to the field name saying that the field is required, but it no longer prevents me from saving my changes.
This is OK for my use-case, I’ll remove the workaround I wrote when I have time
Thanks Adrien and Vince (+ whoever actually made the patch)
1 Like
I’m still seeing the little * next to the field name saying that the field is required, but it no longer prevents me from saving my changes.
Yes that’s because it represents better the DB: the field should not be null, but it’s ok when it actually equals an empty string.
Cheers mate!
! I Hope you are doing fine 
