FazBrowse GitHub Viewer | Trending |
URL:
| Home
Tools: [Download Repo ZIP]   [Original HTTPS Page]

fix: Support delimiters(_-.~) as start or end characters for a segment. by blakeli0 · Pull Request #336 · googleapis/api-common-java · GitHub

This repository was archived by the owner on Sep 27, 2023. It is now read-only.
/ api-common-java Public archive

fix: Support delimiters(_-.~) as start or end characters for a segment. - #336

Merged
blakeli0 merged 2 commits into
mainfrom
support-dot-as-beginning-character
Feb 4, 2022
Merged

blakeli0 merged 2 commits into
mainfrom
support-dot-as-beginning-character

Conversation

blakeli0 commented Feb 3, 2022
edited by Neenu1995
Loading

Copy link
Copy Markdown
Contributor

Support delimiters(_-.~) as start or end characters for a segment if the segment does not contain complex resource names.

  • A segment can start with a delimiter, as long as there is no { right after it.
  • A segment can end with a delimiter, as long as there is no } right before it.
  • A segment like .{well}-{known} or {well}-{known}. is invalid.
  • A segment like .well-known, .well-{known} or .-~{well-known} is considered a literal hence is valid

Fixes #335 ☕️

BEGIN_COMMIT_OVERRIDE
fix: Support delimiters(_-.~) as start or end characters for a segment
END_COMMIT_OVERRIDE

…the segment does not contain complex resource names.
blakeli0 requested review from a team, chanseokoh, meltsufin and vam-google February 3, 2022 23:21

vam-google left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

Choose a reason Spam Abuse Off Topic Outdated Duplicate Resolved Low Quality

LGTM, but please check the seg.length() > 1 check comment first

blakeli0 commented Feb 4, 2022
edited
Loading

Copy link
Copy Markdown
Contributor Author

LGTM, but please check the seg.length() > 1 check comment first

Thanks, I see what you mean now, sorry I misunderstood you earlier. On the other hand, I think the way it is now might be better since it's cleaner and easier to read. Moving seg.length() > 1 would only benefit if the segment contains one character which I think is a very rare case.

blakeli0 merged commit 309521b into main Feb 4, 2022
blakeli0 deleted the support-dot-as-beginning-character branch February 4, 2022 19:00
blakeli0 changed the title Support delimiters(_-.~) as start or end characters for a segment. fix: Support delimiters(_-.~) as start or end characters for a segment. Feb 4, 2022
Neenu1995 added the release-please:force-run To run release-please label Feb 7, 2022
release-please Bot removed the release-please:force-run To run release-please label Feb 7, 2022
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters. Learn more about bidirectional Unicode characters
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

support . a beginning character in path template

5 participants


Back | FazBrowse Home | New Git URL