Frontend implementation for Email Mathesar type

[kgodey]

Requirements

Users should be able to:

• view data in columns that have the Mathesar email custom type
• see validation errors if the data they enter is not a valid email
• change data type to and from the email DB type
• view, set, and change data type options related to email data type
• group data by email-specific grouping options
• filter data by email-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

DB Type Mapping

All columns of this type map to MATHESAR_TYPES.EMAIL. Please note that we should make sure it's available before showing it as an available type.

Implementation

Design

• The Global Data Types spec has the latest version of the UX.
• The Email 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.
  • This should also be used to determine the availability of the email type on a given database. It is a custom type so it's not available on all databases.
• 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)

Additional Context

• Design for email data type #235 (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:
  • Backend work for Mathesar email custom type. #409

[kgodey]

Marking this as ready since filtering and grouping have been moved to other issues and remaining backend work is done.

[seancolsen]

Most of the work here appears to be done, so I'm closing this ticket in favor of a few remaining tickets that are more specific.

To address this ticket's requirements:

• view data in columns that have the Mathesar email custom type

  • This appears to work

• see validation errors if the data they enter is not a valid email

  • This mostly works. Here's what the error looks like.

    

    The error message could be a little more specific. But think it's a small enough issue that I'm not sure it's worth opening a ticket.

• change data type to and from the email DB type

  • Tracked in:

    Unable to convert text column to email #1317

    Unable to convert email column to text #1318

• view, set, and change data type options related to email data type

  • I've gone digging through the specs and not found any type options or display options specified for the Email type.

• group data by email-specific grouping options

  • Tracked in Frontend implementation for type specific grouping options #1073

• filter data by email-specific filtering options

  • Tracked in Frontend implementation for type specific filtering options #1072