nextcloud / nextcloud/forms

Character limit for answers

Open
#3,076 1 comment 1 reaction 0 assignees View on GitHub

Nobody has claimed this yet.

1. to develop enhancement
Dominant language
JavaScript
Stars
382
Forks
127
Avg merge
19h 31m
Merged PRs (30d)
75

Description

Nextcloud (please complete the following information):

  • Nextcloud-Version: 32.0.2
  • Forms-Version: 5.2.3

Is your feature request related to a problem? Please describe.
When using the data collected via the form elsewhere (e.g. in print or on a web page), space there might be limited. Therefore it could be helpful to set custom character limits for short answers, long texts and other fields.

Describe the solution you'd like
Add a Character limit checkbox to the ... options of the appropriate question types.
Ideally, there would also be an indication of this limit when filling the form i.e. 18/70 or 52 characters left maybe in the lower right corner of the field.

Describe alternatives you've considered
I guess, this could also be solved by allowing the form creator to enter a regex, against which the answer is checked. While more powerful, it would be harder to use and potentially very confusing for the form filler.

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by locating the question-type option menus for short answers, long texts, and other fields, then find the corresponding answer-entry views. Review how question settings and responses are stored before deciding where the limit belongs. Done means creators can configure a character limit, answers respect it, and the form filler can see the current limit or remaining characters.

Written by the indexing model from the issue text.

Assessment

Tech stack
javascript
Domain
frontend
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
38/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.