102c42b14b
`qmk find`: usability improvements ( #20440 )
2023-05-20 22:14:43 +10:00
751316c344
[CLI] Add a subcommand for getting information about a keyboard ( #8666 )
...
You can now use `qmk info` to get information about keyboards and keymaps.
Co-authored-by: Erovia <Erovia@users.noreply.github.com>
2020-05-26 13:05:41 -07:00
3db41817e0
Code cleanup, use pathlib, use pytest keyboard
...
Clean up checks and logics that are unnecessary due to MILC updates.
Use pathlib instead of os.path for readability.
Use the 'pytest' keyboard for the tests.
Add community layout for 'handwired/onekey/pytest' so we can test
community layouts.
2020-02-15 15:19:03 -08:00
8eeab1112a
Fix commandline parsing and flake8 findings, rebase
...
Fixed commandline and config parsing. Thx @xplusplus.
Rebased on master and fixed merge conflicts.
2020-02-15 15:19:03 -08:00
988bfffca2
Major rework, no regex/globbing, more walking
...
Instead of using regexes and globbing to find the rules.mk and keymap.c
files, walk the directory tree to find them.
Also, do away with the concept of revision.
2020-02-15 15:19:03 -08:00
3ed1223678
Drop bs4 dependency, update docs, minor improvements
2020-02-15 15:19:03 -08:00
d257a98cb8
Fix regex for parsing rules.mk files
...
I don't know why it couldn't put it together before... ¯\_(ツ)_/¯
2020-02-15 15:19:03 -08:00
26f53d38d9
Another major refactoring, add documentation
...
Move all useful functions to the qmk module and use the cli subcommand
as a wrapper around it.
Add both inline comments and documentation.
2020-02-15 15:19:03 -08:00
Ryan
Zach White
Erovia