You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We currently have a range implementation that accounts for zero items, where it sets a range of 0-100, this should be expanded to encompass all result sets.
Acceptance Criteria
A minimum range implementation should be implemented for partial result sets
Assumptions and Questions
This should help to minimize display shifts that are deceptive ... i.e 0-100 having the same weight as 0-1
What is the minimum range we should implement? 0-10, 0-15, 0-25, 0-50, 0-100?
As of 20190726 this is what happens when a partial result set populated with zeros is returned from the API... part of this is the GUI implementation wasn't expecting zero result sets, this could be a fluke, but as a fallback we should probably take this into account
The text was updated successfully, but these errors were encountered:
Description
We currently have a range implementation that accounts for zero items, where it sets a range of 0-100, this should be expanded to encompass all result sets.
Acceptance Criteria
Assumptions and Questions
0-100
having the same weight as0-1
The text was updated successfully, but these errors were encountered: