-
Updated
Oct 6, 2020 - Python
typing
Here are 357 public repositories matching this topic...
-
Updated
Feb 29, 2020
-
Updated
Sep 8, 2020 - JavaScript
-
Updated
Mar 29, 2020 - JavaScript
-
Updated
Sep 15, 2020 - Python
-
Updated
Nov 8, 2019 - Python
-
Updated
Sep 11, 2020 - JavaScript
-
Updated
Sep 4, 2020 - JavaScript
-
Updated
Jun 6, 2020 - Python
-
Updated
Feb 3, 2017 - JavaScript
Currently there is no way to view history
It would be great if I could see how much I'm improving using this typing test if we stored all the previous WPM, Accuracy scores in a local file.
Solution
At the end of a typing run, pressing a button should show the entire history as a list
Something like this:
| date | time | wpm | Accuracy |
---------------------------------
-
Updated
May 29, 2019 - Java
-
Updated
Jul 13, 2020 - Python
-
Updated
Jun 19, 2020 - Python
-
Updated
Sep 12, 2020 - Shell
-
Updated
Aug 26, 2020 - Python
-
Updated
Apr 20, 2020 - JavaScript
We get the return annotation for free, so we should allow users to do something with it.
Just fix tests to use Factory instead of old style
-
Updated
Apr 9, 2019 - HTML
Hi,
Will it be possible to add support for optional configuration files, the same general idea as ConfigArgParse: https://github.com/bw2/ConfigArgParse
The idea is to be able to pass a file path as an argument and some additional arguments.
the logic should be to first parse the config file and then parse the rest of the arguments.
Thank you!
Improve this page
Add a description, image, and links to the typing topic page so that developers can more easily learn about it.
Add this topic to your repo
To associate your repository with the typing topic, visit your repo's landing page and select "manage topics."
Elm has the option to output errors as JSON (via a flag), and something like that is handy for writing tooling around it. I'm trying to integrate
pytypeinto ALE and this would make it a lot easier.