coderedcorp / coderedcorp/coderedcms

Allow commas in comma separated form choices

Open
#166 3 comments 0 reactions 0 assignees View on GitHub
Area: Core ⚙ Good First Issue hacktoberfest skill: python skill: wagtail Type: Bug
Dominant language
Python
Stars
765
Forks
154
PR merge metrics
No merged PRs in 30d

Description

It is a common use-case to require a comma in a form choice, such as "Please specify your income: $1,000 - $2,000" etc. I think it would be preferable to use pipe separator since it is not an English grammatical character.

While we do have a very customized form page, we are still leaning on some underpinnings of wagtail.contrib.forms, so I think we will either need to provide our own choice field, or make a contribution to wagtail to support changing it from the hard-coded comma.

Contributor guide

No contributing guide indexed for this repository

Research direction

Start by tracing the choice parsing used by wagtail.contrib.forms and compare it with the repository's customized form page. Determine whether a configurable pipe separator or a separate choice field is appropriate. Done means choices containing commas, such as "$1,000 - $2,000", are accepted without splitting at the comma.

Written by the indexing model from the issue text.

Assessment

Tech stack
django, python
Domain
backend
Issue type
Feature
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.