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

Use const keys in pathToRegexp example #416

Merged
merged 1 commit into from
Feb 20, 2024
Merged

Conversation

silverwind
Copy link
Contributor

pathToRegexp does not create a new array and it couldn't even work if it did because the variable binding would be lost. So this can be const and it does also match the module's docs:

https://github.com/pillarjs/path-to-regexp#path-to-regexp-1

`pathToRegexp` does not create a new array and it couldn't even work if it did because the variable binding would be lost. So this can be `const` and it does also match the module's docs:

https://github.com/pillarjs/path-to-regexp#path-to-regexp-1
Copy link

codesandbox bot commented Feb 20, 2024

Review or Edit in CodeSandbox

Open the branch in Web EditorVS CodeInsiders

Open Preview

Copy link

stackblitz bot commented Feb 20, 2024

Review PR in StackBlitz Codeflow Run & review this pull request in StackBlitz Codeflow.

Copy link

codecov bot commented Feb 20, 2024

Codecov Report

All modified and coverable lines are covered by tests ✅

Comparison is base (1f6964f) 100.00% compared to head (d143a88) 100.00%.

Additional details and impacted files
@@            Coverage Diff            @@
##                v3      #416   +/-   ##
=========================================
  Coverage   100.00%   100.00%           
=========================================
  Files            1         1           
  Lines            1         1           
=========================================
  Hits             1         1           

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

Copy link
Owner

@molefrog molefrog left a comment

Choose a reason for hiding this comment

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

👍

@molefrog molefrog merged commit 1fe98bb into molefrog:v3 Feb 20, 2024
4 checks passed
@silverwind silverwind deleted the patch-1 branch February 20, 2024 15:56
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.

None yet

2 participants