You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Nov 6, 2022. It is now read-only.
I recently used the free version of block lab and found a bug/possible enhancement (you decide - I can write patch if needed).
To reproduce:
Add a new block (name it whatever)
Add a new field. Make the field type "email"
On the default value, make it "foo"
Close the field using the "Close Field" button
OPTIONAL: Add other fields. I added 12 before I tried to publish.
Try to publish the new block.
There is no visible warning. If you try to publish prior to step 4, you will see a warning that pops up using bootstrap validation on the default value field. Once the field is closed, there was no visible warning.
Browser: Chrome/OSX
Why: We often add many fields and change many field values prior to saving. since you can only have one field inspector open at a time, if the error occurs in a closed field, there is no warning. This causes a bit of confusion.
Resolution: Global warning? Switch validation to occur on the field close event and cancel the close until the problem is rectified?
The text was updated successfully, but these errors were encountered:
I recently used the free version of block lab and found a bug/possible enhancement (you decide - I can write patch if needed).
To reproduce:
There is no visible warning. If you try to publish prior to step 4, you will see a warning that pops up using bootstrap validation on the default value field. Once the field is closed, there was no visible warning.
Browser: Chrome/OSX
Why: We often add many fields and change many field values prior to saving. since you can only have one field inspector open at a time, if the error occurs in a closed field, there is no warning. This causes a bit of confusion.
Resolution: Global warning? Switch validation to occur on the field close event and cancel the close until the problem is rectified?
The text was updated successfully, but these errors were encountered: