[FEATURE] Builtin high-level predefined patterns - #105
Open
Arun0A wants to merge 5 commits into
Open
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Description
The idea of this PR is highly motivated from #94.
I have implemented 8 new symbols that have predefined regex patterns.
They are:
I have written/performed tests to verify their implementation.
Apart from this, while I was trying to build it from source initially, the build failed due to a package (
clap_lex) requiring edition2024 (cargo feature). This was primarily due to cargo re-resolving dependencies during build, however this could be fixed using the--lockedflag during build to use the existing lockfile in the repo. I also updated the readme to use locked installs due to this reason.Type of change