Conversation
I've just started to look how it works (on local instance) and seems it works fine for new sprints! Might be just my impression but fetching data from Phabricator seems to be slower (it takes some time before graphs are plotted etc). Have you also noticed something similar? When selecting sprint that has ended (thus snapshot data is being fetch) I am getting the following error message: I haven't really looked at the code yet. |
Yes, it seemed slower for projects with >100 tasks which I guess makes sense since it now does multiple HTTP requests for those. Correct, snapshots aren't supposed to work yet since they don't have the JSON structure that the |
public function queryTasksByProject($projectPHID) | ||
/** | ||
* Uses maniphest.search to search tasks for a project. | ||
* @param $projectPHID |
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.
it is a string, right?
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.
Yes! Fixed
So I had a look at the code and:
So basically I'd consider this PR as ready to merge if @jakobw didn't mention cleaning up the commit list a bit. At least "Fix foo" commits could be probably joined with relevant commits. Then I'd be happy to merge. Very nice job! |
ee4d70c
to
c49c578
Compare
@wmde-manicki Squashed the commits! I also think it's fine to fix the status issue later and I agree that some of the stuff in the |
Task: https://phabricator.wikimedia.org/T127179
Things this patch includes:
maniphest.search
instead of `maniphest.query´TaskDataFetcher
that replaces what were previously API calls to fetch tasksTaskDataProcessor
(anyone got an idea for a better name?) that creates a list ofTask
objects from the output ofTaskDataFetcher
Task
which is a value object for tasksTaskList
andTaskListTest
and put it where it belongs (mostlyTaskDataProcessor
,StatusByWorkboardDispatcher
and their tests)StatusByStatusFieldDispatcher
got a little bit uglier since information whether a task is closed is not included inmaniphest.search
so it now checks for a list of hardcoded statuses which might be silly... whew, did I just rewrite Phragile?
These commits should probably be squashed before merging.