Adjust max_length attributes to better fitting values #36
Labels
No labels
Security
TeX
auto-update
board
done
board
ready
board
todo
check
delete-eslint-rc-js
check
update-builddeps-package-json
check
update-eslint-rc-js
check
update-gitignore
check
update-merge-request-template
check
update-prettier-ignore
check
update-pyproject-toml
check
update-renovate-json
check
update-tox-ini
part
backend
part
ci
part
docs
part
frontend
part
i18n
part
non-technical
part
packaging
prio
1
prio
2
prio
3
release-mr-5.x
size
large
size
medium
size
small
source
customer
source
customer::fsmw
source
customer::fss
source
customer::teckids
source
downstream
type
breaking
type
bug
type
feature
type
refactoring
workflow
blocked
workflow
confirmed
workflow
current-todo
workflow
discussing
workflow
new-app
workflow
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
aleksis/AlekSIS-App-Hjelp#36
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
FAQSection.name: 200 → 255IssueCategory.name: 40 → 255IssueCategory.placeholder: 100 → 255created merge request !122 to address this issue
mentioned in merge request !122
Please provide a rationale on why this should be changed, i.e. why the current lengths are problematic.
The UI components used to show these attributes don't have a limit for a specific character amount. Thus there is no reason to force users to be within 100 or even 40 characters.
Issue categories or placeholders are very often longer than 40 characters and sometimes even longer than 100 characters.
The texts ae used in headlines which should be one line al lthe way up to 200% zoom on an average screen.
I can only see one text that is used in a headline (FAQ section name) which already has a limit of 200. From 200 to 255 isn't a big step then. In general, we don't control the circumstance mentioned by you using character limits – just take a look at the
max_lengthattributes of all Core models.So, if you advocate for not having a limit, why do you implement a limit of 255?
mentioned in commit
94c059fa7d