-
Notifications
You must be signed in to change notification settings - Fork 246
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Separate files for configuration #1644
Comments
We have been thinking about this and this is definitely a direction I want to pursue. Eventually, you'll be able to configure In fact, we are planning to build this as part of the submodules (see #1286) feature, where leaving such a configuration file next to a namespaced export ( |
I've actually shifted around here a bit, and I think it'd be better to have the alternate source of jsii configuration be a user-owned |
Does that mean users now have to provide I think it still causes confusion. Ideally Another problem would be, |
I actually would rather have configuration that does not involve/allow logic. Is there anything in particular you have in mind where logic would be needed/useful? |
In situations, like I want to use different configurations based on environments, this logic helps. Similar examples have been followed by libraries like Having a possibility to allow logic can make this configuration extensible. |
This issue has not received any attention in 2 years. If you want to keep this issue open, please leave a comment below and auto-close will be canceled. |
🚀 Feature Request
Affected Languages
TypeScript
orJavascript
Python
Java
C#
,F#
, ...)General Information
Description
Through the readme of the package I found that this package takes configuration through
package.json
file. Although this works fine but makes my package.json file quite big and messy. I prefer to keep most of the part ofpackage.json
auto updating. Would it be a good feature if you can take all that configuration which does not directly affect package.json through a separate configuration file?I am coming from an example where packages like
eslint
,babel
,husky
,lint-staged
who can take configuration through pacakge.json but, also give alternatives likejs
file,yaml
file orjson
file. With this my package.json is pretty small and does not depend on the plugins and their configurations(apart from their dependency).It also opens new possibilities. Like if you are taking configuration through
js
file, then it allows developers to write their logic to export those configurations. For example I can separate configurations based on local, test and production environments.Proposed Solution
Hence, I am proposing a feature using which configurations can be taken through separate files too.
The text was updated successfully, but these errors were encountered: