Frontend implementation for Text Mathesar type

[kgodey]

Requirements

Users should be able to:

• view data in columns that have the Mathesar data type of text (TEXT, VARCHAR. CHAR)
  • columns with large amounts of text should expand when selected
• change data type to and from text DB types
• view, set, and change data type options related to text data types
• group data by text-specific grouping options
• filter data by text-specific filtering options

Update:

• Grouping will be handled in Frontend implementation for type specific grouping options #1073
• Filtering will be handled in Frontend implementation for type specific filtering options #1072

Implementation

Design

• The Global Data Types spec has the latest version of the UX.
• The Text Data Types spec has an older version of the UX but more information on user scenarios.

Backend

• /api/v0/tables/ lists the name and DB type of each columns
• /api/v0/tables/<id/columns/ lists column information in more detail
• /api/v0/databases/<id>/types/ maps Mathesar types to DB types and provides a list of filtering and grouping options per-type.
  • These should be used to populate the filter and grouping options dynamically.
• Updates to column types and type options should happen via PATCH requests to /api/v0/tables/<id>/columns/<id>/. These updates include
  • Changes to the data type (type)
  • Changes to the data type options (type_options)

Additional Context

• Design for text data type #234 (design)
• Mapping DB data types to Mathesar data types #269 (concept of Mathesar types)
• Implement showing and changing a column's type #498 (conversation about data types)
• Blocked by backend work:
  • Handle VARCHAR data type in the backend. #404
  • Handle TEXT data type in the backend. #405
  • Handle CHAR data type in the backend. #407
  • Implement filtering options for Text types. #406
  • Implement grouping for Text types. #408