-
Notifications
You must be signed in to change notification settings - Fork 57
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
Added docstring and type annotations to family(), removed parameter endpoint #87
Open
mattkeanny
wants to merge
10
commits into
ip-tools:main
Choose a base branch
from
mattkeanny:docstr1
base: main
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
Changes from all commits
Commits
Show all changes
10 commits
Select commit
Hold shift + click to select a range
5ee383a
type annotation for family api, py3.8
mattkeanny e73ec40
removed unused parameter from family(), compliant with ops specs.
mattkeanny 61536a1
fixed linter error
mattkeanny 04bf1b9
Merge branch 'ip-tools:main' into docstr1
mattkeanny a44e0ee
restored method signature for family(), added deprecation warning.
mattkeanny 8d0ac8f
added example to docstring
mattkeanny c8559e4
minor reformatting of docstring
mattkeanny d8423bb
Merge branch 'ip-tools:main' into docstr1
mattkeanny 6848489
added type hints to public api of ops client
mattkeanny 67ff393
added examples to docstring
mattkeanny File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains 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
Oops, something went wrong.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
If we are 100% sure on this, let's do it. Otherwise, it would also be a breaking change, if, by chance, the parameter would still be used/needed in some cases.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I tested the family() method, and the implementation allows
endpoint
to be assigned one of the allowed values for the parameterconstituents
and still work as ifconstituents
was assigned the value. Although not according to ops specs, the resulting url when using e.g.endpoint="biblio"
is the same as ifconstituents=["biblio"]
was used.So removing it may indeed break code out there. I'd leave that for a major version upgrade. Fine with the deprecation warning.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Hi Matt. Apologies for the delay.
I am currently not totally sure, it has been a while... Do you agree that we want to keep
endpoint=endpoint
? It looks like the patch hasn't changed yet.On the other hand, I don't want to be too pedantic about it if you think it will be good to go.