-
Notifications
You must be signed in to change notification settings - Fork 452
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
Add config Importer API #299
Comments
Would be handy if we could specify a path to a custom |
I agree. I'd prefer to store the I think that this use case might be applicable to other beautifiers as well. |
This issue has been automatically marked as stale because it has not had recent activity. If this is still an issue, please add a comment. It will be closed if no further activity occurs. Thank you for your contributions. |
This issue has been automatically marked as stale because it has not had recent activity. If this is still an issue, please add a comment. It will be closed if no further activity occurs. Thank you for your contributions. |
Should add more to this list. |
This will be implemented in Unibeautify: https://github.com/Unibeautify/unibeautify-options-importer |
Import configurations from external sources:
.csscomb.json
file.jsbeautifyrc
fileSome of these are already implemented internally. These should be moved out into reusable components using an API of some form, similar to how Beautifiers now work after #282.
The text was updated successfully, but these errors were encountered: