-
-
Notifications
You must be signed in to change notification settings - Fork 43
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Missing histogram data for Nov 15, 2010 #612
Comments
The ranking lenses (top 1000, 10000… 1 million) were only added from May 2021 so didn’t exist for 2010. |
One could argue that we shouldn't show start/end options for dates that we know are not supported by the lens. For example, some metrics provide a min/max date when we know about its availability window. Perhaps we should do the same for lenses. httparchive.org/config/reports.json Lines 118 to 125 in 5a63e50
|
Potentially, but can also result in fighting the GUI and confusing users. For example I'm in 10k lens (only available for 2022). I want as much WordPress data as possible. If the date was filtered, I might not realise there is a lot more than for 10k, and at the very least there's two steps. So both ways have their downfalls. Maybe a better option would potentially be to leave the date pickers alone, but use an error message (where it's less obvious what the limits are than for the timeseries):
|
as a general rule, I suppose, if error could be precalculated\predicted, it's better to notify user beforehand |
Reopening so we can continue thinking through our options |
would it be possible to change it from dropdown to choicefiled? |
@alex-bender any interest in drafting that in a pull request? |
sure, will try to do that tomorrow |
Any progress on this @alex-bender |
Hey, thanks for the ping. Looks like I can win longest stalled issue challenge. If there should be error message or notification, where should it be placed. In what case should it be displayed and so on.. |
https://cdn.httparchive.org/reports/top1k/2010_11_15/speedIndex.json
The text was updated successfully, but these errors were encountered: