Redesign import preview UX

[pavish]

Our import preview UX doesn't match the rest of the application, since it was one of the first pages designed. We should update it. Some specific problems and related issues/discussions are listed below.

Column type selection in preview page varies entirely with the type selection on the table

Description

Upon file upload, the preview page displays a list of database types.

In our table, we display the mathesar types and we do not allow directly setting the database type

Expected behavior

We should have similar UX in both these places since it may confuse users otherwise. However, we might want to only show few configuration options in the preview page.

Related discussions

• Should we consider removing the import preview option? #1242
• Design for suggesting display options #1227

[pavish]

@kgodey @ghislaineguerin Marking this issue as draft until both of you could take a look and add any additional detail if required.

[kgodey]

This is because we designed the import preview page way before we figured out data types. I think we should address this in the UI Styling milestone since that's where we'll be making sure what we've built is consistently styled (I've moved it there).

[kgodey]

We need an updated design for this, so marking as draft.

[vrutik2809]

While importing the data, one file named <file_name>_<id>.csv is created in .media directory.
So, when the user cancels the import then it would be better to delete that file from the directory to utilize the space efficiently.

[kgodey]

Assigning this to @pavish to close since he's implementing this.