Skip to content
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

fix bad text values in parse #126

Merged
merged 1 commit into from
Feb 8, 2024

Conversation

connor4312
Copy link
Contributor

Previously sibling text tokens would exclude the output from the first token, resulting in the referenced issues. I think this should be a fairly safe change.

Fixes #125
Fixes #100

Previously sibling `text` tokens would exclude the `output` from the
first token, resulting in the referenced issues. I think this should
be a fairly safe change.

Fixes micromatch#125
Fixes micromatch#100

const expected = [
['bos', { output: '', value: '' }],
['text', { output: 'foo.', value: 'foo.' }],
Copy link
Contributor Author

Choose a reason for hiding this comment

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

This was just a ., which is what issue #100 referenced

['bos', { output: '', value: '' }],
['text', { output: 'foo.', value: 'foo.' }],
['paren', { output: undefined, value: '(' }],
['text', { output: 'm|c|', value: 'm|c|' }],
Copy link
Contributor Author

Choose a reason for hiding this comment

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

This was |c| which is what #125 referenced

@jonschlinkert
Copy link
Member

Sorry for the late reply, and thanks for the PR. Reviewing now!

@jonschlinkert jonschlinkert merged commit 2677de2 into micromatch:master Feb 8, 2024
@connor4312 connor4312 deleted the issue-125 branch February 8, 2024 16:21
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
2 participants