We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
path_segments
None
s3://bucket
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
The docs for Url::path_segments state:
Url::path_segments
Unless this URL is cannot-be-a-base, return an iterator of ‘/’ slash-separated path segments, each as a percent-encoded ASCII string. Return None for cannot-be-a-base URLs. When Some is returned, the iterator always contains at least one string (which may be empty).
Unless this URL is cannot-be-a-base, return an iterator of ‘/’ slash-separated path segments, each as a percent-encoded ASCII string.
Return None for cannot-be-a-base URLs.
When Some is returned, the iterator always contains at least one string (which may be empty).
However for a URL like s3://bucket the method returns None despite the URL not being a cannot-be-a-base according to the value's debug representation:
Url { scheme: "s3", cannot_be_a_base: false, username: "", password: None, host: Some(Domain("bucket")), port: None, path: "", query: None, fragment: None }
The text was updated successfully, but these errors were encountered:
scheme://domain
No branches or pull requests
The docs for
Url::path_segments
state:However for a URL like
s3://bucket
the method returnsNone
despite the URL not being a cannot-be-a-base according to the value's debug representation:The text was updated successfully, but these errors were encountered: