[JIRA] Improve typing experience of Jira instanziation#1644
Open
halfow wants to merge 1 commit into
Open
Conversation
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Hi!
Sorry for this out of the blue, just got a bit annoyed when using the Jira API. Made a little patch for my self and thought that the community would like it aswell.
Make
Jira()type nicer with inheritance of parent function signature. Works well when just passing through*args**kwargs.Note:
g(f(x))calling overhead of the decorator should not be noticeable as theJiraobject only init once.Patch provides completion capabilities for more editors:
Credits to typing#769 for the pattern.