New user, creates first table, let's say they call it "Customers". They see a table with "Field 1" and two buttons at the bottom, one saying "Save Customers" and the other saying "Clear". It's a bit confusing.
It might be better if the save and clear buttons appear only once the user starts entering data.
This will require dispatch of change in a debounced way from the various property types, rather than on:blur as is currently the case.
Changed made today hide the save button until some data is changed in the new record row via on:blur dispatch of change. The UX is not terrible, but keeping this ticket to see how on:blur user tests
New user, creates first table, let's say they call it "Customers". They see a table with "Field 1" and two buttons at the bottom, one saying "Save Customers" and the other saying "Clear". It's a bit confusing.
It might be better if the save and clear buttons appear only once the user starts entering data.
This will require dispatch of change in a debounced way from the various property types, rather than on:blur as is currently the case.