-
Notifications
You must be signed in to change notification settings - Fork 4k
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
StepFunctions: Label regex incorrect - denies s
literal
#29764
Comments
thanks for reporting this and submitting a PR @piurafunk . I see your PR has been reviewed and approved by CDK Team owner but its not updated with main branch code, thats why its not merged yet. |
Thanks, I hadn't noticed that. I've updated it just now. |
This is now resolved via the referenced PR. |
|
Comments on closed issues and PRs are hard for our team to see. If you need help, please open a new issue that references this one. |
Describe the bug
When adding a label to a
DistributedMap
, the regex denies a string that contains ans
. The regex is hereIt also doesn't deny white space, which the
\s
is supposed to do at the front:My
DistributedMap
definition:Expected Behavior
The inverse of these 2 examples. With an
s
should be fine, with whitespace should be denied.Current Behavior
s
is denied, whitespace is allowed.Reproduction Steps
Possible Solution
My guess is that it's related to the quoting in a JS file. When node interprets it, the
\
characters are being interpreted by Node and stripped out, rather than by the RegEx[ object. When I build the RegExp object, Node CLI prints without\
characters:It seems it's not being gathered correctly. The
\s
becomes justs
, and even the last closing bracket is missing, from the 2nd unicode grouping.I tried submitting a PR, but it was closed due to redtape: #29763
I submitted a 2nd one, this one didn't get automatically closed: #29765
Additional Information/Context
No response
CDK CLI Version
2.135.0
Framework Version
No response
Node.js Version
v20.12.1
OS
Docker - Alpine
Language
TypeScript
Language Version
No response
Other information
No response
The text was updated successfully, but these errors were encountered: