-
Notifications
You must be signed in to change notification settings - Fork 19
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
Round the usage percentage to 1 decimal point #1044
Comments
@jcscottiii how do I get the percentage chart. All I could see now is subtest count chart. |
@jcscottiii I believe this PR is about the chromium usage column on the Overview page? If so, then I believe this feature has already been implemented. I just confirmed now. |
Thank you both for looking into this issue. To clarify, the chart functionality you're interested in is not yet live on the site. However, the current implementation exists in the following file: webstatus.dev/frontend/src/static/js/components/webstatus-feature-usage-chart-panel.ts Lines 57 to 60 in ecbd307
If either of you plan to work on implementing this feature, please let me know along with an estimated ETA. This will help us avoid duplicate effort and ensure a fair opportunity for all contributors. |
I'd like to work on implementing this feature. However, I've been trying to setup the dev container for webstatus.dev, but I keep on running into an error when connecting to the dev container. I'm working on resolving it now though. After I'm able to setup my Dev container, my expected ETA would be 24 hours. |
I get this error from the log when trying to connect to the dev container
Any pointers on how to move on from here will be greatly appreciated! Note:
|
Thanks for the clarification, @jcscottiii! |
Hi @jcscottiii , I'd like to work on this and can complete it by 3rd April or sooner. |
Currently the usage percentage has a large and not very useful number of decimal points. Rounding it to 1 decimal point should be sufficient for all use cases that we currently know of.
The text was updated successfully, but these errors were encountered: