-
Notifications
You must be signed in to change notification settings - Fork 11
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
More freedom for incrementor.enums.values regex #43
Comments
Thanks for the feedback! I really want to get this extension back in working order so any help in the form of PRs you can offer would be greatly appreciated. I'll have to double check the code to see if everything still functions without much regex restriction. |
Actually I'm thinking it's probably best to just have a custom list with some defaults set. (Aside from the numbers) |
Probably my regex won't work with Thanks. |
I have created a Pull Request with the code and included a video. #44 vokoscreenNG-2024-10-11_02-32-00.mp4 |
Good work! From the video it seems to work well but I can also try it out locally to be sure. I think I might have to do some research to see if there's a better way to select what the extension needs without getting confused in situations like the ones you described. But either way I'll try out your PR and if it works well locally I can merge it. Thanks again! |
Thanks for this extension.
I want to do something a bit more complex, like toggle between comparators or booleans operators, something like this
The problem is the regular expression for is too restrictive:
It is possible to change
"^\\w(?:\\-?\\w+)*$"
to"^\\S(?:\\-?\\S+)*$"
? Maybe is a breaking change.I can make a PR if is accepted.
The text was updated successfully, but these errors were encountered: