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
I like the idea of having the formatted percentage (e.g., "92.34%") in the API, otherwise if we store the plain integers, I'd rather we store something like 0.9234 rather than 92.34. Then, the README/status website don't have to do any additional formatting and can use the response as-is. I think I'll just update the README alt text instead. Is that ok?
I like the idea of having the formatted percentage (e.g., "92.34%") in the API, otherwise if we store the plain integers, I'd rather we store something like 0.9234 rather than 92.34. Then, the README/status website don't have to do any additional formatting and can use the response as-is. I think I'll just update the README alt text instead. Is that ok?
Both "92.34%" and 0.9234 (not rounded?) make sense. The API could also contain both.
namcxn
pushed a commit
to namcxn/uptime-monitor
that referenced
this issue
Mar 2, 2023
See for instance https://github.com/aureooms/monitor/blame/master/README.md#L19. It seems upptime/uptime-monitor#45 would fix this error (I cannot comment there since the conversation is limited to collaborators). I originally thought upptime/uptime-monitor#45 would fix the same kind of bug in the generated PWA, however I was wrong.
The text was updated successfully, but these errors were encountered: