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
Is your feature request related to a problem? Please describe.
Every time a table is created, 3 empty rows are created. I believe the table should be empty.
A user needs to delete those 3 rows each time they create a table, as those almost never those are useful and cause issues when a non-nullable column is created and the user doesn't realise there are 3 rows (since they are totally empty and not that easy to spot).
Describe the solution you'd like
I personally believe adding empty rows on creation can be a dark pattern.
My suggestions:
just remove the feature
add a setting to disable it
add a "new table template" the user can change
The text was updated successfully, but these errors were encountered:
The three pre-populated rows are an intentional design choice to help new users get started more easily by reducing the "blank canvas anxiety". While I understand your concern about empty rows, Teable's bulk delete feature makes cleanup quite simple compared to field configuration work.
We'll keep your feedback in mind as we continue to improve the product. Feel free to share any other thoughts you may have.
I agree with alexfacciorusso, your points also make sense, however it would be best practice from other experiences, if a table has no records, a link to create a new record is in place just under the columns names, left aligned. This helps users understand the hext action they need to take. Hope this make sense.
+1 on this request. When a new table needs a required column with no default an error is presented so you have to delete the rows and then make the change again.
Uh oh!
There was an error while loading. Please reload this page.
Is your feature request related to a problem? Please describe.
Every time a table is created, 3 empty rows are created. I believe the table should be empty.
A user needs to delete those 3 rows each time they create a table, as those almost never those are useful and cause issues when a non-nullable column is created and the user doesn't realise there are 3 rows (since they are totally empty and not that easy to spot).
Describe the solution you'd like
I personally believe adding empty rows on creation can be a dark pattern.
My suggestions:
The text was updated successfully, but these errors were encountered: