Frontend implementation for Boolean Mathesar type

[kgodey]

Requirements

Users should be able to:

• view data in columns that have the Boolean Mathesar type
• change data type to and from the BOOLEAN DB type
• view, set, and change data type options related to the Boolean data type
• filter data by Boolean-specific filtering options
• use display options to view data in Boolean type columns
  • The checkbox display option should display data as checkboxes
  • The dropdown display option should display data as dropdowns and only allow boolean options to be input
  • If custom labels are selected, the labels for the dropdowns should be adjusted accordingly.

Update:

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

DB Type Mapping

There is only one DB type mapping to this UI type, so no special mapping rules are necessary.

Implementation

Design

• The Global Data Types spec has the latest version of the UX.
• The Boolean Data Type spec has an older version of the UX but more information on user scenarios.
• The NULL values spec has requirements for displaying and editing NULL values within checkbox columns. (See "Scenario 1c" and "Scenario 2c".)

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 for boolean data type #237 (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 BOOLEAN data type in the backend #387
  • Implement filtering options for Boolean types #388
  • Implement display options for Boolean types #390