Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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
Migrate [Jira] services to new service model #2541
Migrate [Jira] services to new service model #2541
Changes from 1 commit
ad30bcf
65f78cf
b640b5d
9fb8817
070dec5
File filter
Filter by extension
Conversations
Jump to
There are no files selected for viewing
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.
:protocol(http|https)
seems clearer.:path*
to allow multiple path segments.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.
👍 on protocol
path
is where I kept hitting a a mental wall with the pattern. I was trying to use nested non-capture groups but pattern was having none of it 😆 Let me see if I can clean that up a bitThere 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.
I ended up using a specific regex (
(.+)
) for the host param, which works and is more consistent with the legacy service info (which did not explicitly differentiate host and path)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.
I'm fine with the change you made, though I think
hostAndPath
would better describe the field for the user (this is with #2496 in mind).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.
yeah I like that better too (and that's what was there before so +1 for consistency!)
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.
changed to
hostAndPath
in both the example pattern, route pattern, and param to handle for consistency. I elected not to include the+
suffix but let me know if it is needed(original comment) i'm probably being overly pedantic here, but just noticed the example pattern before was actually
hostAndPath+
does the+
suffix have any significance in the example patterns/is it worth including?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.
In a pattern, the + tells pathToRegexp to allow one or more segments instead of just one, zero or one, or zero or more. We aren’t doing anything using the pattern in the examples beyond parsing it to get the individual segments. (That’s forthcoming actually, in #2496)