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

fix non conforming search link resolution and update to 0.3.5 #179

Merged

Conversation

philvarner
Copy link
Collaborator

Related Issue(s): #177

Description:

  • fix handling of search link in non-conforming API

PR Checklist:

  • Code is formatted
  • Tests pass
  • Changes are added to the CHANGELOG

@philvarner philvarner marked this pull request as ready for review May 26, 2022 15:17
@codecov-commenter
Copy link

Codecov Report

Merging #179 (1495cb8) into release/0.3.5 (64ec0c1) will not change coverage.
The diff coverage is 100.00%.

@@              Coverage Diff               @@
##           release/0.3.5     #179   +/-   ##
==============================================
  Coverage          81.00%   81.00%           
==============================================
  Files                  9        9           
  Lines                558      558           
==============================================
  Hits                 452      452           
  Misses               106      106           
Impacted Files Coverage Δ
pystac_client/client.py 78.68% <100.00%> (ø)
pystac_client/version.py 100.00% <100.00%> (ø)

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 64ec0c1...1495cb8. Read the comment docs.

@philvarner philvarner merged commit 6d76ff7 into release/0.3.5 May 26, 2022
@philvarner philvarner deleted the pv/fix-non-conforming-search-link-resolution branch May 26, 2022 15:43
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

4 participants