Skip to content

Conversation

@givensuman
Copy link

This closes #549 and potentially closes #505 as well.

The call to wrap in the previous implementation appears to fail when the input already appears to be wrapped which occurs with named capture groups as discovered in the aforementioned issue.

@givensuman givensuman requested a review from danielroe as a code owner October 16, 2025 13:03
@vercel
Copy link

vercel bot commented Oct 16, 2025

Someone is attempting to deploy a commit to the Nuxt Team on Vercel.

A member of the Team first needs to authorize it.

@givensuman givensuman closed this by deleting the head repository Dec 15, 2025
Copy link
Member

@danielroe danielroe left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

oops, looks like i missed this one.

did you mean to close it?

@givensuman
Copy link
Author

I was deleting old forks and it looks like that's automatic behavior. Not sure if it's still usable/relevant but if it is feel free to re-open.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

maybe()/optionally() incorrectly handles named capture Unexpected maybe() result

2 participants