Add slider component

[jaaydenh]

[bpmct]

This will be awesome for stuff like tolerance!! Could we also support sliding between several pre-defined "string" options in a specific order. For example

Edit: fixed image

[jaaydenh]

Yes definitely possible. btw I use this site for inspiration and to save time with implementing new components, https://originui.com/slider

[Emyrk]

@bpmct We are quite limited on the syntax to represent this.

Here is the current hcl syntax for a slider

data "coder_parameter" "temperature" {
  name = "temperature"
  display_name = "AI Temperature"
  type = "number"
  form_type = "slider"
  default = 50
  count = 1

  validation {
    min = 0
    max = 100
  }
}

How do you propose we best represent the metadata for the slider? We are currently limited by the terraform provider to a completely static schema. So we could add something like:

data "coder_parameter" "temperature" {
  name = "temperature"
  // ...
  slider_metadata = {
    tick_labels = {
      "Cold" = 0
      "Balanced" = 50
      "Creative" = 100
    }
  }
}

This would mean we would have <type>_metdata for every form type that we want to add custom styling too. These blocks would obviously grow and grow, requiring bumping the terraform provider for each change. Now our terraform provider version is basically tracking form_metadata changes. Which.... is not ideal imo.

Arbitrary metadata field

The alternative is to place arbitrary data into a shared metadata block. This is currently impossible without these changes @johnstcn looked into: coder/terraform-provider-coder#354

data "coder_parameter" "temperature" {
  name = "temperature"
  // ...
  form_type_metadata = {
    // Literally put anything you want in here
    // An example:
    tick_labels = {
      "Cold" = 0
      "Balanced" = 50
      "Creative" = 100
    }
  }
}

Today to accomplish this, we would have to do this:

data "coder_parameter" "temperature" {
  name = "temperature"
  // ...
  form_type_metadata = jsonencode({
    // Literally put anything you want in here
    // An example:
    tick_labels = {
      "Cold" = 0
      "Balanced" = 50
      "Creative" = 100
    }
  })
}

[bpmct]

This would mean we would have _metdata for every form type that we want to add custom styling too. These blocks would obviously grow and grow, requiring bumping the terraform provider for each change. Now our terraform provider version is basically tracking form_metadata changes. Which.... is not ideal imo.

This feels a bit safer than arbitrary an metadata that we have to read for each field, so it is my slight preference. I know both are not ideal. WIll honestly defer to y'all here.

[jaaydenh]

Going to create another issue to handle custom styling on form controls such as sliders as there is still some decisions to make.

For actually implementing this on the frontend. I would push for either arbitrary metadata or styling defined outside terraform.

One issue I can anticipate is edge case in the display of the forms because of the limitations on how to express the styling. These will feel like bugs and it will be more difficult to make the UI responsive to all possible form states.