The Wayback Machine - https://web.archive.org/web/20200717102243/https://github.com/topics/developer-experience
Skip to content
#

developer-experience

Here are 195 public repositories matching this topic...

iiroj
iiroj commented Dec 16, 2019

The README.md contains a lot of advanced config examples for functional tasks. We should probably add some basic ones as well:

  1. '*.js': ['eslint'] <- fail when eslint finds issues issues
  2. '*.js': ['eslint --fix', 'git add'] <- automatically fix eslint issues, and add to commit
  3. '*.js': ['prettier --list-different'] <- fail when prettier finds issues
  4. `'*.js': ['prettier --write
backstage
freben
freben commented Apr 22, 2020

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:

  • Let all public, published packages retain their @backstage namespace.
  • Change all private packages in the open source project (plugins/home-page, plugins/welcome) to be under an @internal names

Improve this page

Add a description, image, and links to the developer-experience topic page so that developers can more easily learn about it.

Curate this topic

Add this topic to your repo

To associate your repository with the developer-experience topic, visit your repo's landing page and select "manage topics."

Learn more

You can’t perform that action at this time.