Skip to content

bug: dynamic parameters do not indicate optional params #22045

@andrewhamon

Description

@andrewhamon

Is there an existing issue for this?

  • I have searched the existing issues

Current Behavior

With legacy params, an optional parameter is clearly labeled as optional:

Image

With dynamic params enabled, fields are no longer indicated as optional:

Image

Relevant Log Output

Expected Behavior

Optional fields should be clearly labeled as such.

Steps to Reproduce

  1. make a template with an optional param (i.e. has a default value)
  2. turn on Dynamic Parameters in template settings
  3. make a new workspace
  4. observe the UI

Environment

  • Host OS: irrelevant
  • Coder version: 2.28.8

Additional Context

The issue occurs consistently

Metadata

Metadata

Assignees

No one assigned

    Labels

    needs-triageIssue that require triage

    Type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions