-
Notifications
You must be signed in to change notification settings - Fork 110
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
Future support for Rufo #202
Comments
Multi formatter support is already implemented and has been stable for a long time. So you can already choose another formatter for Ruby if you like. Nevertheless, we should have a good default. If it turns out rufo will no longer be maintained, we should make another formatter the default. (Personally, I use rufo and like it a lot so I hope they can find a new maintainer to keep the project going.) |
@lassik Okay 👍🏽 Even I have been using rufo as well. It's pretty good. Hopefully it will continue to be maintained. Will keep an eye out of something else comes as well. |
The simplest is to try |
rufo maintenance continues 😃 |
Excellent. @kzkn, thank you very much for continuing the maintenance of this excellent formatter. rufo has always been the default Ruby formatter for format-all, so it seems no action is necessary :) |
The default formatter for ruby is
rufo
. The maintainer is seeking new maintainers for it. Not sure, how this is going to progress over time.In the unfortunate event of
rufo
becoming not maintained what do we plan to use?Is the adding of configurable multi formatters going to help with this by allowing to choose what we require in case of such scenarios?
Reference: ruby-formatter/rufo#272
The text was updated successfully, but these errors were encountered: