User Settings: Expose user settings in server

[btmorr]

overview

Run app should be able to query the server for a list of settings to include in the "Advanced Settings" page.

behavior

Schema:

{
  "settings": [
    {
      "title": "Calibrate to bottom of well",
      "description": "Perform labware calibration by moving the tip to the bottom-center of the well rather than the top-center (which is the default if this option is unset)",
      "value": true
    },
    {
      "title": "Other setting",
      "description": "Long description of next setting",
      "value": false
    }
  ]
}

There should be a GET endpoint that returns a title, long description, and current value for each setting in "feature_flags", and any other settings that we wish to expose through the advance settings page.

[mcous]

Here's my pass at a spec. @btmorr and @Laura-Danielle let me know what you think

fetch settings

request

GET /settings

response

{
  "settings": [
    {
      "id": "short-identifier-1",
      "title": "User-facing title",
      "description": "User-facing description",
      "type": "boolean",
      "value": true
    },
    {
      "id": "short-identifier-2",
      "title": "User-facing title",
      "description": "User-facing description",
      "type": "number",
      "value": 42
    }
  ]
}

set settings

request

POST /settings

body

{
  "id": "short-identifier-1",
  "value": false
}

response

(Same response as GET /settings)

{
  "settings": [
    {
      "id": "short-identifier-1",
      "title": "User-facing title",
      "description": "User-facing description",
      "type": "boolean",
      "value": false
    },
    {
      "id": "short-identifier-2",
      "title": "User-facing title",
      "description": "User-facing description",
      "type": "number",
      "value": 42
    }
  ]
}

[btmorr]

Omitting "type" field for now--currently only supporting booleans