Skip to content
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

Study description: remove characters limits #5988

Closed
elisabettai opened this issue Jun 21, 2024 · 1 comment · Fixed by #5989
Closed

Study description: remove characters limits #5988

elisabettai opened this issue Jun 21, 2024 · 1 comment · Fixed by #5989
Assignees
Labels

Comments

@elisabettai
Copy link
Collaborator

elisabettai commented Jun 21, 2024

Long Story Short
I try to insert this string as a study description: "Pre-operative workflow for spinal cord injury rehabilitation with an analysis and planning system"

And the I get a very cryptic error
422_error_modify_description

This is because there's a limit of 100 characters. This limit is not needed anymore, because the description goes in a scrollable container (just confirmed this with @odeimaiz)

Solutions

  1. Preferred: remove the characters limit
  2. Mitigation: show a clear message to the user. The backend actually gives a pretty informative message:
    image

Actual behaviour
The user doesn't know what's going on

Steps to reproduce

  1. Go to osparc.io (or any other deployment)
  2. Click on a study card and put a long string in the description
@elisabettai
Copy link
Collaborator Author

elisabettai commented Jun 21, 2024

Assigning all the backenders, as I imagine this is an easy bug to fix. If not, please let me know and we discuss (at the next planning?) @GitHK, @pcrespov @sanderegg, sorry for the spam. 😊

@pcrespov pcrespov added this to the South Island Iced Tea milestone Jun 21, 2024
@pcrespov pcrespov transferred this issue from ITISFoundation/osparc-issues Jun 21, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants