Replies: 1 comment
|
Indeed I believe it should be an error for new collection (if we are able to detect it) but it was put as a warning for all the existing collections without readme. But then again since validation happens only at publish time we could indeed transform it as an error |
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
If an author publishes a collection without a README, it is currently flagged as a
warningduringnpm run validate. We can considering changing this to an error, as providing a README should be mandatory. This is a recommended best practice that helps users understand the collection when it is opened in the extension.All reactions