click
click copied to clipboard
Document existing parser fully
The existing Click API is very large and a lot of edge cases are undocumented. Additionally there are lots of combinations between parameters and options.
I am not sure what is the best way to document all the combinations. There are enough combinations that it is hard to remember them all. Maybe a table with with tests that correlate to the table entry?
The test suite is getting better. May have an idea for splitting into situations and kwargs.
The reference docs per situation are decent for options, arguments, and parameters sections.