Currently , some work item widgets have props passed to them and some fetch the results from the work item query.
In order for each widget to be placed anywhere and not dependent on passing too many computed props, we need to make sure there is uniformity and the only props passed to each widget should be iid and fullPath because that is the unique pair to fetch any work item.
Simon Knoxchanged title from Refactor/clean widgets to only use id/iid and fullPath to fetch work item in individual widget and not paas any props from work_attributes_wrapper to Refactor/clean widgets to only use id/iid and fullPath to fetch work item in individual widget and not pass any props from work_attributes_wrapper
changed title from Refactor/clean widgets to only use id/iid and fullPath to fetch work item in individual widget and not paas any props from work_attributes_wrapper to Refactor/clean widgets to only use id/iid and fullPath to fetch work item in individual widget and not pass any props from work_attributes_wrapper
yes , also because A couple of other feature issues are marked as Deliverable in %17.1 . I can confirm after a week to see where I stand in the progress of the issues
But ofcourse, if someone else has the capacity would be great to have it in this milestone
yes , also because A couple of other feature issues are marked as Deliverable in %17.1
@deepika.guliani@psimyn 17.1 ~Deliverables haven't quite been determined yet. The ones with the labels are ones that came from previous milestones. I should have them removed later today. For now, I'll add this to %17.1 and will remove it if it doesn't fit in our allotment of typemaintenance issues.
@deepika.guliani Sorry, I thought I had included this in %17.1. Are you comfortable with keeping it in %17.1, overall team-wise we have the capacity to keep it in %17.1?
@donaldcook Just wanted to confirm that this issue might be at risk since I have a couple more issues in 17.4 other than rollups changes , which might make it difficult to be completed in 17.4.
@deepika.guliani@psimyn Moving the work item query to each widget component would result in fetching the work item n times for n widgets. We don't have a query to only fetch widget data, without all the work item data, right?
Also, we need to know if that work item type has that widget enabled, so we would still need to query for the work item widgets in the parent to see if we should render that widget component. Because of that, it feels like having it as is decreases the amount of queries fetched, no? Am I missing something?