Extending shared config in JSON
See original GitHub issuePrettier already support sharing-configurations. However it’s lacking support for extending shared configurations.
I’m thinking it could work like this
// .prettierrc.json
{
"$schema": "http://json.schemastore.org/prettierrc",
"extends": "@myorg/prettier-config", // shared config
"printWidth": 120 // override
}
Issue Analytics
- State:
- Created 4 years ago
- Reactions:12
- Comments:11 (3 by maintainers)
Top Results From Across the Web
Configuration File - Prettier
This means you can configure Prettier via (in order of precedence):. A "prettier" key in your package.json file. A .prettierrc file written in...
Read more >How to extend cypress.json config to other configuration files?
Cypress plugin that adds "extends" support to the configuration file. This allows the config files to remain DRY and avoid duplicating data, ...
Read more >Extending the Cypress Config File
Notice that we return merged base config plus config JSON (not the config argument passed into the plugins file). Cypress will automatically re- ......
Read more >Shareable Config Presets - Renovate Docs
If you're using a renovate.json file to share your presets, ... To use a preset put it in an extends array within your...
Read more >Configuration Files - ESLint - Pluggable JavaScript Linter
Here's an example JSON configuration file that uses the typescript-eslint parser to support TypeScript syntax: { "root": true, "extends": ...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
need reopen vscode ,and then it works @fisker
Copy and paste is not an option when you want to maintain a huge organisation, if we decide for a change, instead of a npm install update, it would be “copy-pasting” over so many repositories which may not even be possible to get someone to go over ALL projects.