Skip to content

Delimiter field for multiple choice dropdown #17

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
michael-valdron opened this issue Apr 17, 2025 · 2 comments
Closed

Delimiter field for multiple choice dropdown #17

michael-valdron opened this issue Apr 17, 2025 · 2 comments
Assignees

Comments

@michael-valdron
Copy link

Description

Not sure if this the right place to request this but feel free to move if not.

I'd like to open this feature request to allow for the override of the delimiter used to separate multiple values selected under a multiple choice dropdown field.

Issue Form Example

Use field attributes.delimiter to override the default ,:

name: Bug report
description: 🐞 Report a bug
labels:
  - bug
body:
  - type: dropdown
    attributes:
      label: Select value(s)
      description: Choose one or more value(s) this bug to have.
      multiple: true
      attributes:
        delimiter: \n
      options:
        - foo
        - bar
        - world
    validations:
      required: true

Rendered Example

If foo and bar are selected:

### Select value(s)
foo
bar
@ncalteen
Copy link
Collaborator

Hello! Thanks for submitting this feedback! Unfortunately this is probably not the right repository, since this project consumes and parses the rendered Markdown from the issue form. If this was implemented, though, it would definitely be something that impacts this project.

In the meantime, it might be best to create a new discussion post in the GitHub discussions page.

@ncalteen ncalteen self-assigned this Apr 18, 2025
@michael-valdron
Copy link
Author

Hello! Thanks for submitting this feedback! Unfortunately this is probably not the right repository, since this project consumes and parses the rendered Markdown from the issue form. If this was implemented, though, it would definitely be something that impacts this project.

In the meantime, it might be best to create a new discussion post in the GitHub discussions page.

@ncalteen Thanks for the follow up!

I've opened a discussion post about this feature request at the reference: https://github.com/orgs/community/discussions/157091

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants