Closed ergorion closed 3 years ago
I think it's not possible to trace why this happens, but maybe we the solution is then to catch the exception in the searchWorkitemFullItem method and just omit that result.
Would that be acceptable?
I agree that it's not possible to trace/avoid this, it seems to happen on the server side. I have tried a different approach: instead of omitting the result (could be one, could be more), my solution breaks the method searchWorkitemFullItem into a new searchWorkitem that only returns the ids (as default), and then the rest functionality to fetch each workitem completely.
Maybe you would like to check out my modified branch? In addition, I added support for approvees (trying to hang on to your style as much as possible). If you like the change, feel free to take it over, I do not want to start a seperate project/branch.
I took your solution, made the tests and some improvements. Thanks for the contribution. Feel free to re-open if you find any issues. This will be released after i fix up the other open issues :)
I know that this workitem exists, I can look at it in the web userinterface. However, when I try to get it, I get an exception. In addition, this breaks my search with projet.searchWorkitemFullItem() -- as the function also fetches all workitems from the server. When it tries to retrieve this problematic work item, the exception breaks the complete search.