This repository has been archived by the owner on Oct 15, 2021. It is now read-only.
feat: enable to define baumeister config in package.json #270
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
mischah
added a commit
that referenced
this pull request
Feb 18, 2019
This way we can get rid of the following files: ``` /.babelrc /.eslintrc.json /.prettierrc /.stylelintrc.json /baumeister.json ``` It’s a trend that tools make it possible to store their settings in a field in the `package.json`. I recently enabled Baumeister to handle his configuration this way. See [#270 – feat: enable to define baumeister config in package.json](#270). I’d like the approach, because the project root is less cluttered with dotfiles and you can see all the configs in one place.
mischah
added a commit
to micromata/generator-baumeister
that referenced
this pull request
Feb 20, 2019
This way we can get rid of the following files: ``` /.babelrc /.eslintrc.json /.prettierrc /.stylelintrc.json /baumeister.json ``` It’s a trend that tools make it possible to store their settings in a field in the `package.json`. I recently enabled Baumeister to handle his configuration this way. See [#270 – feat: enable to define baumeister config in package.json](micromata/Baumeister#270). I’d like the approach, because the project root is less cluttered with dotfiles and you can see all the configs in one place.
mischah
added a commit
to micromata/generator-baumeister
that referenced
this pull request
Feb 20, 2019
This way we can get rid of the following files: ``` /.babelrc /.eslintrc.json /.prettierrc /.stylelintrc.json /baumeister.json ``` It’s a trend that tools make it possible to store their settings in a field in the `package.json`. I recently enabled Baumeister to handle his configuration this way. See [#270 – feat: enable to define baumeister config in package.json](micromata/Baumeister#270). I’d like the approach, because the project root is less cluttered with dotfiles and you can see all the configs in one place.
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
You now can decide to store your settings either in a file called
baumeister.json(respectively.baumeister.json) or in abaumeisterkey in yourpackage.jsonfile 🎉