The unofficial WWDC app for macOS
-
Updated
Jul 16, 2020 - Swift
As part of clarifying what is part of the open source offering and what is examples or private code, we should signal these differences using package names/namespaces.
Suggested solution:
@backstage namespace.plugins/home-page, plugins/welcome) to be under an @internal namesAdd a description, image, and links to the developer-experience topic page so that developers can more easily learn about it.
To associate your repository with the developer-experience topic, visit your repo's landing page and select "manage topics."
The README.md contains a lot of advanced config examples for functional tasks. We should probably add some basic ones as well:
'*.js': ['eslint']<- fail when eslint finds issues issues'*.js': ['eslint --fix', 'git add']<- automatically fix eslint issues, and add to commit'*.js': ['prettier --list-different']<- fail when prettier finds issues