Frontend implementation for Money Mathesar type

[kgodey]

Requirements

Users should be able to:

• view data in columns that have the Money Mathesar type
• change data type to and from the associated DB types based on options selected
  • MATHESAR_TYPES.MONEY_[XXX]
  • MONEY
• view, set, and change data type options related to the Money data types
• filter data by Money-specific filtering options
• group data by Money-specific grouping options
• use display options to view data in Money type columns
  • Data should be rounded according to the precision specified in the display options
• see Money data shown in a monospace font or using tabular figures (see design spec)
• see Money data formatted according to the locale of the currency

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

• If the custom MATHESAR_TYPES.MONEY type is available:
  • all new columns of UI type Money should use it.
  • converting existing columns to the UI type Money should use it.
• If the custom MATHESAR_TYPES.MONEY type is not available:
  • all new columns of UI type Money or converting existing columns to UI type Money should use default MONEY type

Existing columns of type MONEY can only be converted to MATHESAR_TYPES.MONEY if MATHESAR_TYPES.MONEY is available by converting first to Number and then converting back to Money.

Please note that the design for MONEY vary on whether MATHESAR_TYPES.MONEY is installed.

Implementation

Design

• The Global Data Types spec has the latest version of the UX.
• The Money Data Type 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 display options (display_options)

Additional Context

• Design work:
  • Design for money data type #239
  • Update design for money data type options #655
• 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 money custom type  #417
  • Handle MONEY data type in the backend. #420
  • Custom money type #1094
  • Implement display options for the custom Money type #1105