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

Not translated error message in creation report form #6680

Closed
lndrtrbn opened this issue Apr 12, 2024 · 0 comments · Fixed by #6700
Closed

Not translated error message in creation report form #6680

lndrtrbn opened this issue Apr 12, 2024 · 0 comments · Fixed by #6700
Assignees
Labels
bug use for describing something not working as expected solved use to identify issue that has been solved (must be linked to the solving PR)

Comments

@lndrtrbn
Copy link
Member

Description

The error message for length in the form to create report is not translated. It's an automatic message generated by Yup.

image

image

In the screen above, we can see that no message is given to the constraint "min".

Environment

  1. OS (where OpenCTI server runs): Edge
  2. OpenCTI version: 6.0.x
  3. OpenCTI client: frontend
  4. Other environment details:

Reproducible Steps

Steps to create the smallest reproducible scenario:

  1. Go to reports page
  2. Click on Add button
  3. Fill name input with one letter only

Expected Output

Error in your language

Actual Output

Error generic from Yup in english only

@lndrtrbn lndrtrbn added bug use for describing something not working as expected needs triage use to identify issue needing triage from Filigran Product team labels Apr 12, 2024
@SamuelHassine SamuelHassine added this to the Release 6.1.0 milestone Apr 12, 2024
@jborozco jborozco removed the needs triage use to identify issue needing triage from Filigran Product team label Apr 15, 2024
@CelineSebe CelineSebe self-assigned this Apr 15, 2024
CelineSebe added a commit that referenced this issue Apr 16, 2024
Signed-off-by: Celine Sebe <celine.sebe@filigran.io>
@CelineSebe CelineSebe linked a pull request Apr 16, 2024 that will close this issue
5 tasks
CelineSebe added a commit that referenced this issue Apr 16, 2024
Signed-off-by: Celine Sebe <celine.sebe@filigran.io>
CelineSebe added a commit that referenced this issue Apr 16, 2024
Signed-off-by: Celine Sebe <celine.sebe@filigran.io>
CelineSebe added a commit that referenced this issue Apr 16, 2024
Signed-off-by: Celine Sebe <celine.sebe@filigran.io>
@SamuelHassine SamuelHassine added the solved use to identify issue that has been solved (must be linked to the solving PR) label Apr 16, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug use for describing something not working as expected solved use to identify issue that has been solved (must be linked to the solving PR)
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants