fix: answer range format validation and error message in Numerical input

[ihor-romaniuk]

Backport Pull Requests to frontend-lib-content-components: openedx-unsupported/frontend-lib-content-components#511

Description

These fixes validate input range format; it accepts the following response forms: [1,10], [1, 10], [ 1,10 ], [ 1, 10 ], [1, 10 ] , [ 1, 10], [1.1,10], [1.1,10.1], [1.1,10.1] and display error on incorrect format like: [1.10], [1;10], [1/10], etc.

Steps to reproduce

1. Go to studio -> unit -> problem -> Numerical input
2. In answers click on Add answer button -> Add answer range
3. Fill in value [5.8), click Save (like user set dot instead of comma by mistake)

Actual result

Nothing happened, in console there's error

Note: the same when user print additional bracket

Expected result

Some validation should be for field or some error message for user should be shown
Before save:

After save:

Note

Old closed MR #1557

[openedx-webhooks]

Thanks for the pull request, @ihor-romaniuk!

This repository is currently maintained by @bradenmacdonald.

Once you've gone through the following steps feel free to tag them in a comment and let them know that your changes are ready for engineering review.

🔘 Get product approval

If you haven't already, check this list to see if your contribution needs to go through the product review process.

• If it does, you'll need to submit a product proposal for your contribution, and have it reviewed by the Product Working Group.
  • This process (including the steps you'll need to take) is documented here.
• If it doesn't, simply proceed with the next step.

🔘 Provide context

To help your reviewers and other members of the community understand the purpose and larger context of your changes, feel free to add as much of the following information to the PR description as you can:

• Dependencies

  This PR must be merged before / after / at the same time as ...

• Blockers

  This PR is waiting for OEP-1234 to be accepted.

• Timeline information

  This PR must be merged by XX date because ...

• Partner information

  This is for a course on edx.org.

• Supporting documentation
• Relevant Open edX discussion forum threads

🔘 Get a green build

If one or more checks are failing, continue working on your changes until this is no longer the case and your build turns green.

---

Where can I find more information?

If you'd like to get more details on all aspects of the review process for open source pull requests (OSPRs), check out the following resources:

• Overview of Review Process for Community Contributions
• Pull Request Status Guide
• Making changes to your pull request

When can I expect my changes to be merged?

Our goal is to get community contributions seen and reviewed as efficiently as possible.

However, the amount of time that it takes to review and merge a PR can vary significantly based on factors such as:

• The size and impact of the changes that it introduces
• The need for product review
• Maintenance status of the parent repository

💡 As a result it may take up to several weeks or months to complete a review and merge your PR.

[codecov]

Codecov Report

❌ Patch coverage is 93.33333% with 1 line in your changes missing coverage. Please review.
✅ Project coverage is 94.65%. Comparing base (a7860b8) to head (cf8e336).
⚠️ Report is 10 commits behind head on master.

Files with missing lines	Patch %	Lines
...ntainers/ProblemEditor/data/ReactStateOLXParser.js	66.66%	1 Missing ⚠️

Additional details and impacted files

@@            Coverage Diff             @@
##           master    #2426      +/-   ##
==========================================
+ Coverage   94.63%   94.65%   +0.02%     
==========================================
  Files        1180     1180              
  Lines       26151    26164      +13     
  Branches     5836     5824      -12     
==========================================
+ Hits        24747    24766      +19     
+ Misses       1333     1327       -6     
  Partials       71       71              

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
• 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

[brian-smith-tcril]

Not blocking, just adding context to the failing codecov check.

It seems codecov isn't considering this line as covered

[bradenmacdonald]

I think there is a bug with negative numbers. Negative numbers should be allowed, but it's showing them as an error: