This PR attempts to separate 'obtaining the data' (GithubRaw) and 'validation' (Github).
Currently I have just managed to move the metadata code across to the new file github.ml.
This need some thought - the current design is rather ugly. For example, I have separated a GithubRaw.Issue and a Github.Project, which have mostly the same fields but the Github.Project has the metadata parsed (the idea was that Issue is Github speak, but for Nowwhat a project is an issue but with some key metadata). Also, the code runs more slowly because it there is now the additional step of looping through the entire issue list after navigating the query body.
This PR attempts to separate 'obtaining the data' (
GithubRaw) and 'validation' (Github).Currently I have just managed to move the metadata code across to the new file
github.ml.This need some thought - the current design is rather ugly. For example, I have separated a
GithubRaw.Issueand aGithub.Project, which have mostly the same fields but theGithub.Projecthas the metadata parsed (the idea was thatIssueis Github speak, but for Nowwhat a project is an issue but with some key metadata). Also, the code runs more slowly because it there is now the additional step of looping through the entire issue list after navigating the query body.