-
-
Notifications
You must be signed in to change notification settings - Fork 5.5k
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
Integrate new path-to-regexp with trailing optionals [appveyor azuredevops npm gitlab date githubmanifest githubpackage jenkins matrix readthedocs requires shippable snyk wordpress] #2644
Conversation
|
How do folks feel about merging this with the github link in place while we wait for a published version? I don't love the idea, but if it's temporary I don't mind too much. |
Generally speaking I avoid doing so, but agree that if this is temporary (seems like that should be merged and published soon) then it is probably okay, especially considering the benefits of the trailing optional |
@@ -25,8 +25,7 @@ class GithubManifestVersion extends ConditionalGithubAuthService { | |||
static get route() { | |||
return { | |||
base: 'github/manifest-json/v', | |||
format: '([^/]+)/([^/]+)/?([^/]+)?', | |||
capture: ['user', 'repo', 'branch'], | |||
pattern: ':user/:repo/:branch?', |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Sidenote, I'm seeing an invalid response data
badge message for the example badge used here. Seeing this in prod too so not related to this PR.
https://img.shields.io/github/manifest-json/v/RedSparr0w/IndieGala-Helper.svg
@@ -23,8 +23,7 @@ class GithubPackageJsonVersion extends ConditionalGithubAuthService { | |||
static get route() { | |||
return { | |||
base: 'github/package-json/v', | |||
format: '([^/]+)/([^/]+)/?([^/]+)?', | |||
capture: ['user', 'repo', 'branch'], | |||
pattern: ':user/:repo/:branch?', |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Ditto on example error here
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Did you mean to add something like (branch) to the title? I've just gone ahead and done that.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Sorry I should've been more clear. I meant that this badge is showing an invalid response data
error with the example too (also occurs in prod so not related to these changes)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good! Inline question below on wordpress service, and a couple other thoughts not directly related to these changes
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Think this is good to go! I may open a separate issue to deal with those erorring examples
Could you re-up this @calebcartwright? Every time a merge conflict has to be resolved manually the review gets dismissed. |
Fix #2497
Ref pillarjs/path-to-regexp#176