-
Notifications
You must be signed in to change notification settings - Fork 3
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
format
behavior change
#50
Comments
I'll also work on this one |
Great! Before you get started, I just want to ping the rest of the team and ensure what this issue proposes (originally an idea from @adthrasher ) is exactly what we want. @claymcleod and @peterhuene haven't weighed in yet. |
I think this is fine from a next step perspective. It's also relatively straightforward. I do think we should consider doing what |
I agree. What's proposed in this issue is kind of a stop-gap to improve the UX immediately. It shouldn't be the behavior long-term, but it's good enough for now. @Scott8440 you have the go-ahead to start work on this! Really appreciate your contributions :) |
Closed in #51. |
The current default behavior of
sprocket format
is to accept a single document, format it, and print the result to STDOUT. That isn't very useful in many contexts.We should drop this behavior, and require either the
--overwrite
flag or the (new in #49 )--check
flag.The text was updated successfully, but these errors were encountered: