Julien Reichardt
Julien Reichardt
If you don't see what I mean in the comments, I can push a commit which implements my proposals (after you are done of course). Then, you can review it...
I propose to merge this when the test are executed (somehow) in the CI. Then, I can open a PR to do minor improvements here and there.
Thanks for the contribution! Can you also add a test case for the previously incorrect parsing?
Sounds good to use `Int64` 👍
@veelenga If it is possible to use GitHub Actions, I can do the docs automation myself (I have already done this for some other of my projects) - and no...
Good idea. For battery, it is possible through `/sys/class/power_supply/BAT0`. It will be hard to test because servers don't have ones. For disk usage, the ideal would be to have statfs...
No need to close it @TingPing , I'll rebase my branch on master to continue further #331 .
Ready for reviews again.
By the way the biggest gratitude you can show to support the development is to make a donation.
It can maybe more relevant that the engine ranks first the occurences in titles, for instance like [devdocs](https://devdocs.io). Page results could be added after them.