Distinguish invalid from No match found

Open
#47 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
64/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Quiet
Tech stack
typescript
Domain
frontend

Research direction

Start by reproducing the issue in the UI with "[a-8" as the regular expression and "a" as the test string, then locate the code that handles regex test results. The work is done when valid matches, valid non-matches, and invalid Lucene regexes display distinct states.

Written by the indexing model from the issue text.

Description

An invalid Lucene regex is treated the same as a regex that simply does not match the test string.

Image

I enter: "[a-8" (as regular expression) and "a" (as test string)
the UI shows "No match found".

I think there should be distinction between states like "Match found", "No match found", and "Invalid regex" or "Error".

This would make it less confusing and give better clarity when testing invalid Lucene regexes.

Dominant language
TypeScript
Stars
3
Forks
1
PR merge metrics
No merged PRs in 30d

Getting set up

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.

Similar issues

More TypeScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.