Skip to content
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

go-swagger throws error on Windows if application path contains parentheses #146

Merged
merged 1 commit into from
Oct 9, 2021

Conversation

agmikhailov
Copy link
Contributor

Possible fix for issue: go-swagger throws error on Windows if application path contains parentheses #145

@codecov
Copy link

codecov bot commented May 25, 2021

Codecov Report

Merging #146 (e8e27ff) into master (9b48106) will decrease coverage by 0.02%.
The diff coverage is 60.00%.

Impacted file tree graph

@@            Coverage Diff             @@
##           master     #146      +/-   ##
==========================================
- Coverage   62.95%   62.92%   -0.03%     
==========================================
  Files          28       28              
  Lines        2054     2058       +4     
==========================================
+ Hits         1293     1295       +2     
- Misses        592      593       +1     
- Partials      169      170       +1     
Impacted Files Coverage Δ
schema_loader.go 86.11% <60.00%> (-1.04%) ⬇️

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 9b48106...e8e27ff. Read the comment docs.

@agmikhailov agmikhailov changed the title go-swagger throws error on Windows if application path contains arentheses go-swagger throws error on Windows if application path contains parentheses May 25, 2021
@agmikhailov agmikhailov force-pushed the patch-1 branch 4 times, most recently from 3694094 to 6c40857 Compare May 26, 2021 09:27
…arentheses go-openapi#145

Signed-off-by: Aleksey Mikhaylov <almikhailov@plesk.com>
@youyuanwu youyuanwu requested a review from fredbi May 29, 2021 16:39
@casualjim casualjim merged commit fed826c into go-openapi:master Oct 9, 2021
fredbi added a commit to fredbi/spec that referenced this pull request Dec 4, 2023
A more thorough investigation on loading specs from a generated server
from paths containing special characters (such as blank spaces,
parenthesis) did not conclude that it was necessary to alter how cache
entries are matched.

Indeed, this change deeply altered how keys in the cache are managed
and was therefore at best, a risky bet.

* reverted commit e8e27ff
* added check to ensure that the root pseudo-document is preloaded in
  cache under all conditions
* added more unit tests to check the behavior of the normalizers against
  escaped characters
* closes go-openapi#145

Signed-off-by: Frederic BIDON <fredbi@yahoo.com>
fredbi added a commit to fredbi/spec that referenced this pull request Dec 4, 2023
A more thorough investigation on loading specs from a generated server
from paths containing special characters (such as blank spaces,
parenthesis) did not conclude that it was necessary to alter how cache
entries are matched.

Indeed, this change deeply altered how keys in the cache are managed
and was therefore at best, a risky bet.

* reverted commit e8e27ff
* added check to ensure that the root pseudo-document is preloaded in
  cache under all conditions
* added more unit tests to check the behavior of the normalizers against
  escaped characters
* closes go-openapi#145

Signed-off-by: Frederic BIDON <fredbi@yahoo.com>
fredbi added a commit to fredbi/spec that referenced this pull request Dec 4, 2023
A more thorough investigation on loading specs from a generated server
from paths containing special characters (such as blank spaces,
parenthesis) did not conclude that it was necessary to alter how cache
entries are matched.

Indeed, this change deeply altered how keys in the cache are managed
and was therefore at best, a risky bet.

* reverted commit e8e27ff
* added check to ensure that the root pseudo-document is preloaded in
  cache under all conditions
* added more unit tests to check the behavior of the normalizers against
  escaped characters
* closes go-openapi#145

Signed-off-by: Frederic BIDON <fredbi@yahoo.com>
fredbi added a commit that referenced this pull request Dec 4, 2023
A more thorough investigation on loading specs from a generated server
from paths containing special characters (such as blank spaces,
parenthesis) did not conclude that it was necessary to alter how cache
entries are matched.

Indeed, this change deeply altered how keys in the cache are managed
and was therefore at best, a risky bet.

* reverted commit e8e27ff
* added check to ensure that the root pseudo-document is preloaded in
  cache under all conditions
* added more unit tests to check the behavior of the normalizers against
  escaped characters
* closes #145

Signed-off-by: Frederic BIDON <fredbi@yahoo.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants