Skip to content
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

Remove rubocop #561

Merged
merged 1 commit into from
Oct 8, 2024
Merged

Remove rubocop #561

merged 1 commit into from
Oct 8, 2024

Conversation

Schwad
Copy link
Collaborator

@Schwad Schwad commented Oct 8, 2024

_why didn't use rubocop.

@Schwad Schwad merged commit 8e6d186 into main Oct 8, 2024
1 check passed
@noahgibbs
Copy link
Collaborator

On the one hand, I don't think "_why didn't use Rubocop" wouldn't be enough reason by itself. On the other hand, I 100% agree with this decision :-)

I think Rubocop's emphasis on uniformity is very wrong for both _why and Shoes. We want weird stuff happening in our playpen. And _why was a big fan of weirdness in the interface and the implementation.

@Schwad
Copy link
Collaborator Author

Schwad commented Oct 8, 2024

Totally!

However one biproduct of this is my editor does do a certain amount of autoformatting, which I enjoy in personal coding. so if I touch a file and my editor makes small non-blocking changes I'm unlikely to just go and change my development setup for one repo!

@Schwad
Copy link
Collaborator Author

Schwad commented Oct 8, 2024

just a side note for future PRs

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants