If a user mistypes an option, flag, or command, the error message should include a suggestion for the near-miss.

Example:

% example --indx 5
Error: Unexpected argument '--indx'
       Did you mean '--index'?
Usage: example [--index <index>] [<values> ...]

The rome package will likely be the only package published for users. This will contain the CLI and a very thin API that heavily limits the public API exposed. There's no intention to publish any other packages as this would heavily restrict the changes we can make.

• Custom project finding logic exists that matches th

What does “confirmed” mean? Recently there were discussions on defining confirmed as “tested positive/exhibit symptoms” as opposed to “tested positive/asymptomatic”. Are we looking at daily or cumulative readings? The latter maybe obvious but it would be nice to add a full data description to the repo.

• I have searched the issues of this repository and believe that this is not a duplicate.

Reproduction link

https://next.ant.design/components/table/#components-table-demo-virtual-list

Steps to reproduce

Select "RTL" at the top of the screen. Try sc

Are you submitting a bug report?

Yes

Steps to reproduce

0. Have Wox Settings set to empty query on open
1. Open Wox and enter query, for example "cmd"
2. Press Shift + Enter
3. Run cmd as admin
4. Open Wox again, the "Run as administrator" menu is still shown. Need to press escape twice in order to receive an empty query

Expected behavior: On step 4, when opening Wox it sho

At the bottom of your project page (https://pattle.github.io/simpsons-in-css/) there is a minor typo:

"What's really cool is I can now do stuff like that this..."

You could change it to: "What's really cool is now I can do stuff like this..." or some variant thereof without using the word "that."

Thanks for creating this content! I noticed there is a typo in the pandas, import convention section. It says pasdas instead of pandas. I thought you'd like to know.

A big value of extensions is the BuildItem model.
We need to document them so other extension writers can discover and use them.
They are also part of the extension contract.

1. document all "public" BuildItem with adequate JavaDoc
2. build an anotation processor that will collect the BuildItems and generate a list of them per extension and a documentation (summary?).

sindresorhus/awesome#1394 went stale. Would be nice to finish it at some point. However, awesome-lint could probably be made better first.