Ecosyste.ms: Issues
An open API service for providing issue and pull request metadata for open source projects.
GitHub / NET-A-PORTER/scala-uri issues and pull requests
#128 - update spray-json to avoid vulnerability
Pull Request -
State: closed - Opened by johnduffell over 4 years ago
- 2 comments
#128 - update spray-json to avoid vulnerability
Pull Request -
State: closed - Opened by johnduffell over 4 years ago
- 2 comments
#127 - Link to the new home of scala-uri in README
Pull Request -
State: closed - Opened by theon over 7 years ago
#127 - Link to the new home of scala-uri in README
Pull Request -
State: closed - Opened by theon over 7 years ago
#127 - Link to the new home of scala-uri in README
Pull Request -
State: closed - Opened by theon over 7 years ago
#126 - Spaces encoded as '+' characters don't decode
Issue -
State: open - Opened by subourbonite over 7 years ago
- 2 comments
#125 - Matrix params runtime exception
Pull Request -
State: closed - Opened by Petesta almost 8 years ago
- 2 comments
#124 - Runtime exception on matrixParams
Issue -
State: closed - Opened by Petesta almost 8 years ago
- 1 comment
#124 - Runtime exception on matrixParams
Issue -
State: closed - Opened by Petesta almost 8 years ago
- 1 comment
#124 - Runtime exception on matrixParams
Issue -
State: closed - Opened by Petesta almost 8 years ago
- 1 comment
#123 - Support Scala 2.12
Issue -
State: closed - Opened by Rydgel about 8 years ago
- 7 comments
#123 - Support Scala 2.12
Issue -
State: closed - Opened by Rydgel about 8 years ago
- 7 comments
#123 - Support Scala 2.12
Issue -
State: closed - Opened by Rydgel about 8 years ago
- 7 comments
#122 - toURI for local file
Issue -
State: open - Opened by herriojr about 8 years ago
- 2 comments
#121 - add maven version badge to readme
Pull Request -
State: closed - Opened by emanresusername about 8 years ago
- 2 comments
#121 - add maven version badge to readme
Pull Request -
State: closed - Opened by emanresusername about 8 years ago
- 2 comments
#121 - add maven version badge to readme
Pull Request -
State: closed - Opened by emanresusername about 8 years ago
- 2 comments
#121 - add maven version badge to readme
Pull Request -
State: closed - Opened by emanresusername about 8 years ago
- 2 comments
#120 - Support scala 2.11.8
Pull Request -
State: closed - Opened by putgeminmouth about 8 years ago
- 2 comments
#120 - Support scala 2.11.8
Pull Request -
State: closed - Opened by putgeminmouth about 8 years ago
- 2 comments
#119 - Try(Uri.parse("%error")) still writes a traceback to stdout/stderr
Issue -
State: closed - Opened by cecton about 8 years ago
- 2 comments
#119 - Try(Uri.parse("%error")) still writes a traceback to stdout/stderr
Issue -
State: closed - Opened by cecton about 8 years ago
- 2 comments
#118 - Passing a [/ returns a valid URI?
Issue -
State: closed - Opened by schmitch about 8 years ago
- 1 comment
#118 - Passing a [/ returns a valid URI?
Issue -
State: closed - Opened by schmitch about 8 years ago
- 1 comment
#118 - Passing a [/ returns a valid URI?
Issue -
State: closed - Opened by schmitch about 8 years ago
- 1 comment
#118 - Passing a [/ returns a valid URI?
Issue -
State: closed - Opened by schmitch about 8 years ago
- 1 comment
#117 - DSL for v1
Issue -
State: closed - Opened by evanbennett over 8 years ago
- 3 comments
#116 - UriConfig.withNoEncoding should also disable userInfoEncoder
Pull Request -
State: closed - Opened by evanbennett over 8 years ago
- 1 comment
#116 - UriConfig.withNoEncoding should also disable userInfoEncoder
Pull Request -
State: closed - Opened by evanbennett over 8 years ago
- 1 comment
#116 - UriConfig.withNoEncoding should also disable userInfoEncoder
Pull Request -
State: closed - Opened by evanbennett over 8 years ago
- 1 comment
#115 - URIs the do not have '//' after 'scheme:'
Issue -
State: closed - Opened by evanbennett over 8 years ago
- 1 comment
#115 - URIs the do not have '//' after 'scheme:'
Issue -
State: closed - Opened by evanbennett over 8 years ago
- 1 comment
#114 - A URISyntaxException is thrown parsing the following url: https://krownlab.com/products/hardware-systems/baldur/#baldur-top-mount#1
Issue -
State: closed - Opened by johann-abraham over 8 years ago
- 5 comments
#114 - A URISyntaxException is thrown parsing the following url: https://krownlab.com/products/hardware-systems/baldur/#baldur-top-mount#1
Issue -
State: closed - Opened by johann-abraham over 8 years ago
- 5 comments
#114 - A URISyntaxException is thrown parsing the following url: https://krownlab.com/products/hardware-systems/baldur/#baldur-top-mount#1
Issue -
State: closed - Opened by johann-abraham over 8 years ago
- 5 comments
#114 - A URISyntaxException is thrown parsing the following url: https://krownlab.com/products/hardware-systems/baldur/#baldur-top-mount#1
Issue -
State: closed - Opened by johann-abraham over 8 years ago
- 5 comments
#113 - Fix issue #107 where /path and path were being considered the same
Pull Request -
State: open - Opened by theon over 8 years ago
- 13 comments
#113 - Fix issue #107 where /path and path were being considered the same
Pull Request -
State: open - Opened by theon over 8 years ago
- 13 comments
#113 - Fix issue #107 where /path and path were being considered the same
Pull Request -
State: open - Opened by theon over 8 years ago
- 13 comments
#112 - Feature request: Query string parsing
Issue -
State: closed - Opened by 0xABAB over 8 years ago
- 1 comment
#112 - Feature request: Query string parsing
Issue -
State: closed - Opened by 0xABAB over 8 years ago
- 1 comment
#112 - Feature request: Query string parsing
Issue -
State: closed - Opened by 0xABAB over 8 years ago
- 1 comment
#111 - Having / and ? next to each other isn't possible
Issue -
State: closed - Opened by bjfletcher over 8 years ago
- 2 comments
#111 - Having / and ? next to each other isn't possible
Issue -
State: closed - Opened by bjfletcher over 8 years ago
- 2 comments
#111 - Having / and ? next to each other isn't possible
Issue -
State: closed - Opened by bjfletcher over 8 years ago
- 2 comments
#111 - Having / and ? next to each other isn't possible
Issue -
State: closed - Opened by bjfletcher over 8 years ago
- 2 comments
#110 - incorrect publicSuffix matching
Issue -
State: closed - Opened by brahn almost 9 years ago
- 5 comments
#110 - incorrect publicSuffix matching
Issue -
State: closed - Opened by brahn almost 9 years ago
- 5 comments
#110 - incorrect publicSuffix matching
Issue -
State: closed - Opened by brahn almost 9 years ago
- 5 comments
#110 - incorrect publicSuffix matching
Issue -
State: closed - Opened by brahn almost 9 years ago
- 5 comments
#109 - PR for issues-108
Pull Request -
State: closed - Opened by dkjhanitt almost 9 years ago
- 4 comments
#109 - PR for issues-108
Pull Request -
State: closed - Opened by dkjhanitt almost 9 years ago
- 4 comments
#108 - Support for tld
Issue -
State: closed - Opened by dkjhanitt almost 9 years ago
- 8 comments
#108 - Support for tld
Issue -
State: closed - Opened by dkjhanitt almost 9 years ago
- 8 comments
#108 - Support for tld
Issue -
State: closed - Opened by dkjhanitt almost 9 years ago
- 8 comments
#107 - Domain names are preprended with '/'
Issue -
State: open - Opened by juliendangers almost 9 years ago
- 1 comment
#107 - Domain names are preprended with '/'
Issue -
State: open - Opened by juliendangers almost 9 years ago
- 1 comment
#106 - Encoding seems broken
Issue -
State: closed - Opened by howyp about 9 years ago
- 1 comment
#106 - Encoding seems broken
Issue -
State: closed - Opened by howyp about 9 years ago
- 1 comment
#105 - Parse schemes with PLUS, HYPHEN or DOT
Pull Request -
State: closed - Opened by nlochschmidt about 9 years ago
- 4 comments
#105 - Parse schemes with PLUS, HYPHEN or DOT
Pull Request -
State: closed - Opened by nlochschmidt about 9 years ago
- 4 comments
#104 - Valid characters '+', '-' and '.' in scheme not allowed
Issue -
State: closed - Opened by nlochschmidt about 9 years ago
#104 - Valid characters '+', '-' and '.' in scheme not allowed
Issue -
State: closed - Opened by nlochschmidt about 9 years ago
#103 - Fixes MatrixParam parsing for issue #102
Pull Request -
State: closed - Opened by fsaintjacques over 9 years ago
- 6 comments
#103 - Fixes MatrixParam parsing for issue #102
Pull Request -
State: closed - Opened by fsaintjacques over 9 years ago
- 6 comments
#103 - Fixes MatrixParam parsing for issue #102
Pull Request -
State: closed - Opened by fsaintjacques over 9 years ago
- 6 comments
#102 - Empty Params are not accepted in MatrixParam
Issue -
State: closed - Opened by fsaintjacques over 9 years ago
- 1 comment
#102 - Empty Params are not accepted in MatrixParam
Issue -
State: closed - Opened by fsaintjacques over 9 years ago
- 1 comment
#102 - Empty Params are not accepted in MatrixParam
Issue -
State: closed - Opened by fsaintjacques over 9 years ago
- 1 comment
#102 - Empty Params are not accepted in MatrixParam
Issue -
State: closed - Opened by fsaintjacques over 9 years ago
- 1 comment
#101 - Accept empty passwords in parser
Pull Request -
State: closed - Opened by fchiron over 9 years ago
- 4 comments
#100 - Trailing slashes are not normalized
Issue -
State: closed - Opened by cb372 over 9 years ago
- 3 comments
#100 - Trailing slashes are not normalized
Issue -
State: closed - Opened by cb372 over 9 years ago
- 3 comments
#100 - Trailing slashes are not normalized
Issue -
State: closed - Opened by cb372 over 9 years ago
- 3 comments
#100 - Trailing slashes are not normalized
Issue -
State: closed - Opened by cb372 over 9 years ago
- 3 comments
#99 - Characters after '#' is encoded even if part of valid URL
Issue -
State: closed - Opened by hjz over 9 years ago
- 4 comments
#99 - Characters after '#' is encoded even if part of valid URL
Issue -
State: closed - Opened by hjz over 9 years ago
- 4 comments
#99 - Characters after '#' is encoded even if part of valid URL
Issue -
State: closed - Opened by hjz over 9 years ago
- 4 comments
#99 - Characters after '#' is encoded even if part of valid URL
Issue -
State: closed - Opened by hjz over 9 years ago
- 4 comments
#98 - Upgrade to paraboiled 2.1.0
Pull Request -
State: closed - Opened by crakjie over 9 years ago
- 4 comments
#98 - Upgrade to paraboiled 2.1.0
Pull Request -
State: closed - Opened by crakjie over 9 years ago
- 4 comments
#98 - Upgrade to paraboiled 2.1.0
Pull Request -
State: closed - Opened by crakjie over 9 years ago
- 4 comments
#98 - Upgrade to paraboiled 2.1.0
Pull Request -
State: closed - Opened by crakjie over 9 years ago
- 4 comments
#97 - Equals-signs in URI fragment are unnecessarily escaped
Issue -
State: closed - Opened by JustAHappyKid over 9 years ago
- 1 comment
#97 - Equals-signs in URI fragment are unnecessarily escaped
Issue -
State: closed - Opened by JustAHappyKid over 9 years ago
- 1 comment
#97 - Equals-signs in URI fragment are unnecessarily escaped
Issue -
State: closed - Opened by JustAHappyKid over 9 years ago
- 1 comment
#97 - Equals-signs in URI fragment are unnecessarily escaped
Issue -
State: closed - Opened by JustAHappyKid over 9 years ago
- 1 comment
#96 - Hostnames containing anything other than alphanumerics and periods should fail
Issue -
State: closed - Opened by brujoand over 9 years ago
- 3 comments
#96 - Hostnames containing anything other than alphanumerics and periods should fail
Issue -
State: closed - Opened by brujoand over 9 years ago
- 3 comments
#96 - Hostnames containing anything other than alphanumerics and periods should fail
Issue -
State: closed - Opened by brujoand over 9 years ago
- 3 comments
#96 - Hostnames containing anything other than alphanumerics and periods should fail
Issue -
State: closed - Opened by brujoand over 9 years ago
- 3 comments
#95 - Parsing URI without scheme gives a path instead of (expected) host
Issue -
State: closed - Opened by brujoand over 9 years ago
- 2 comments
#95 - Parsing URI without scheme gives a path instead of (expected) host
Issue -
State: closed - Opened by brujoand over 9 years ago
- 2 comments
#95 - Parsing URI without scheme gives a path instead of (expected) host
Issue -
State: closed - Opened by brujoand over 9 years ago
- 2 comments
#95 - Parsing URI without scheme gives a path instead of (expected) host
Issue -
State: closed - Opened by brujoand over 9 years ago
- 2 comments
#95 - Parsing URI without scheme gives a path instead of (expected) host
Issue -
State: closed - Opened by brujoand over 9 years ago
- 2 comments
#94 - Doesn't encode '@' by default
Issue -
State: closed - Opened by gsastry over 9 years ago
- 2 comments
#94 - Doesn't encode '@' by default
Issue -
State: closed - Opened by gsastry over 9 years ago
- 2 comments
#94 - Doesn't encode '@' by default
Issue -
State: closed - Opened by gsastry over 9 years ago
- 2 comments
#93 - It's not possible to prevent percent encoding of non-ascii letters
Issue -
State: closed - Opened by brujoand over 9 years ago
- 1 comment