As our Issue is primarily a wrapper for PyGithub's github.Issue, the best thing is to make use an instance of that to wrap most of our functionality. It looks like we just need to give the appropriate headers and attributes (which seem to be stored in github.Issue._headers and github.Issue._rawData, respectively, for actual issues). See GithubObject.__init__.
Needs are:
[ ] Test Issue that does have front matter, and one that does not
[ ] Mocks for the underlying _issue.get_timeline() method:
[ ] to handle "labeled" events
[ ] to handle "assigned" event
[ ] Tests for issue methods based on this test setup
[ ] Separate set of tests for all methods in NoIssue
We'll count on PyGithub's testing to ensure that calls to the GitHub API still work.
As our
Issue
is primarily a wrapper for PyGithub'sgithub.Issue
, the best thing is to make use an instance of that to wrap most of our functionality. It looks like we just need to give the appropriateheaders
andattributes
(which seem to be stored ingithub.Issue._headers
andgithub.Issue._rawData
, respectively, for actual issues). SeeGithubObject.__init__
.Needs are:
Issue
that does have front matter, and one that does not_issue.get_timeline()
method:issue
methods based on this test setupNoIssue
We'll count on PyGithub's testing to ensure that calls to the GitHub API still work.