Skip to content

Please remove the 3 empty rows added when creating a table #1225

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

Open
alexfacciorusso opened this issue Jan 6, 2025 · 3 comments
Open

Please remove the 3 empty rows added when creating a table #1225

alexfacciorusso opened this issue Jan 6, 2025 · 3 comments
Labels
question Further information is requested

Comments

@alexfacciorusso
Copy link

alexfacciorusso commented Jan 6, 2025

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:

  1. just remove the feature
  2. add a setting to disable it
  3. add a "new table template" the user can change
@tea-artist
Copy link
Contributor

Thank you for this thoughtful suggestion.

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.

@kpodp0ra kpodp0ra added the question Further information is requested label Jan 7, 2025
@maxNodeJs
Copy link

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.

@ziti
Copy link

ziti commented May 1, 2025

+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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
question Further information is requested
Projects
None yet
Development

No branches or pull requests

5 participants