home.social

#rubocop — Public Fediverse posts

Live and recent posts from across the Fediverse tagged #rubocop, aggregated by home.social.

  1. Did anyone ask for a bunch of #RuboCop bug-fixes? Here you go github.com/rubocop/rubo... Just in time for @[email protected] which is starting tomorrow morning! #Ruby

    Release RuboCop v1.86.2 · rubo...

  2. RuboCop: Layout/LineLength: Line is too long. [81/80]. One character. The centurion is not amused.

    #Rubycon2026 #Ruby #RuboCop #DevHumor #Rimini

  3. RuboCop: Layout/LineLength: Line is too long. [81/80]. One character. The centurion is not amused.

    #Rubycon2026 #Ruby #RuboCop #DevHumor #Rimini

  4. Another rubocop/standardrb gripe:

    Style/EmptyLiteral: Use hash literal {} instead of Hash.new

    Nah, I have my own heuristics for when to use which one. If it's inside a block with braces, I assert that:

    # the "approved" butthole syntax
    let(:params) { {} }

    looks worse than

    # ain't nothing wrong with this
    let(:params) { Hash.new }

    #rubocop #standardrb #ruby

  5. Another rubocop/standardrb gripe:

    Style/EmptyLiteral: Use hash literal {} instead of Hash.new

    Nah, I have my own heuristics for when to use which one. If it's inside a block with braces, I assert that:

    # the "approved" butthole syntax
    let(:params) { {} }

    looks worse than

    # ain't nothing wrong with this
    let(:params) { Hash.new }

    #rubocop #standardrb #ruby

  6. Another rubocop/standardrb gripe:

    Style/EmptyLiteral: Use hash literal {} instead of Hash.new

    Nah, I have my own heuristics for when to use which one. If it's inside a block with braces, I assert that:

    # the "approved" butthole syntax
    let(:params) { {} }

    looks worse than

    # ain't nothing wrong with this
    let(:params) { Hash.new }

    #rubocop #standardrb #ruby

  7. Another rubocop/standardrb gripe:

    Style/EmptyLiteral: Use hash literal {} instead of Hash.new

    Nah, I have my own heuristics for when to use which one. If it's inside a block with braces, I assert that:

    # the "approved" butthole syntax
    let(:params) { {} }

    looks worse than

    # ain't nothing wrong with this
    let(:params) { Hash.new }

    #rubocop #standardrb #ruby

  8. Another rubocop/standardrb gripe:

    Style/EmptyLiteral: Use hash literal {} instead of Hash.new

    Nah, I have my own heuristics for when to use which one. If it's inside a block with braces, I assert that:

    # the "approved" butthole syntax
    let(:params) { {} }

    looks worse than

    # ain't nothing wrong with this
    let(:params) { Hash.new }

    #rubocop #standardrb #ruby

  9. 🎉 Behold, the latest in the never-ending quest to make #Emacs less user-friendly! The #Rubocop creator has decided to grace us with #Neocaml, because apparently OCaml wasn't hard enough already without some #TreeSitter magic. 🤪 Embrace the chaos, developers! 🖥️🔧
    github.com/bbatsov/neocaml #developerchaos #HackerNews #ngated

  10. 🎉 Behold, the latest in the never-ending quest to make #Emacs less user-friendly! The #Rubocop creator has decided to grace us with #Neocaml, because apparently OCaml wasn't hard enough already without some #TreeSitter magic. 🤪 Embrace the chaos, developers! 🖥️🔧
    github.com/bbatsov/neocaml #developerchaos #HackerNews #ngated

  11. 🎉 Behold, the latest in the never-ending quest to make #Emacs less user-friendly! The #Rubocop creator has decided to grace us with #Neocaml, because apparently OCaml wasn't hard enough already without some #TreeSitter magic. 🤪 Embrace the chaos, developers! 🖥️🔧
    github.com/bbatsov/neocaml #developerchaos #HackerNews #ngated

  12. 🎉 Behold, the latest in the never-ending quest to make #Emacs less user-friendly! The #Rubocop creator has decided to grace us with #Neocaml, because apparently OCaml wasn't hard enough already without some #TreeSitter magic. 🤪 Embrace the chaos, developers! 🖥️🔧
    github.com/bbatsov/neocaml #developerchaos #HackerNews #ngated

  13. 🎉 Behold, the latest in the never-ending quest to make #Emacs less user-friendly! The #Rubocop creator has decided to grace us with #Neocaml, because apparently OCaml wasn't hard enough already without some #TreeSitter magic. 🤪 Embrace the chaos, developers! 🖥️🔧
    github.com/bbatsov/neocaml #developerchaos #HackerNews #ngated

  14. This must be one of the best articles about #RuboCop I ever came across lovro-bikic.github.io/300-days

    It made really proud of the work we've done with the project, and the great community around it!

    #Ruby

  15. This must be one of the best articles about #RuboCop I ever came across lovro-bikic.github.io/300-days

    It made really proud of the work we've done with the project, and the great community around it!

    #Ruby

  16. This must be one of the best articles about I ever came across lovro-bikic.github.io/300-days

    It made really proud of the work we've done with the project, and the great community around it!

  17. This must be one of the best articles about #RuboCop I ever came across lovro-bikic.github.io/300-days

    It made really proud of the work we've done with the project, and the great community around it!

    #Ruby

  18. This must be one of the best articles about #RuboCop I ever came across lovro-bikic.github.io/300-days

    It made really proud of the work we've done with the project, and the great community around it!

    #Ruby

  19. RuboCop is pretty awesome. I use it a lot at work to autocorrect generated code, apart from general usage.

    Today was the second time I've written a custom RuboCop formatter, and it's so easy, convenient and quick to do.

    docs.rubocop.org/rubocop/exten

    #RuboCop #Ruby

  20. RuboCop is pretty awesome. I use it a lot at work to autocorrect generated code, apart from general usage.

    Today was the second time I've written a custom RuboCop formatter, and it's so easy, convenient and quick to do.

    docs.rubocop.org/rubocop/exten

    #RuboCop #Ruby

  21. RuboCop is pretty awesome. I use it a lot at work to autocorrect generated code, apart from general usage.

    Today was the second time I've written a custom RuboCop formatter, and it's so easy, convenient and quick to do.

    docs.rubocop.org/rubocop/exten

    #RuboCop #Ruby

  22. RuboCop is pretty awesome. I use it a lot at work to autocorrect generated code, apart from general usage.

    Today was the second time I've written a custom RuboCop formatter, and it's so easy, convenient and quick to do.

    docs.rubocop.org/rubocop/exten

    #RuboCop #Ruby

  23. RuboCop is pretty awesome. I use it a lot at work to autocorrect generated code, apart from general usage.

    Today was the second time I've written a custom RuboCop formatter, and it's so easy, convenient and quick to do.

    docs.rubocop.org/rubocop/exten

    #RuboCop #Ruby

  24. Moar #RuboCop bug-fixes for everyone! github.com/rubocop/rubocop/rel

    Enjoy!

    I also realized we skipped RuboCop 1.83 due to an issue in the release script... Oh, well...

    #ruby

  25. Moar #RuboCop bug-fixes for everyone! github.com/rubocop/rubocop/rel

    Enjoy!

    I also realized we skipped RuboCop 1.83 due to an issue in the release script... Oh, well...

    #ruby

  26. Moar bug-fixes for everyone! github.com/rubocop/rubocop/rel

    Enjoy!

    I also realized we skipped RuboCop 1.83 due to an issue in the release script... Oh, well...

  27. Moar #RuboCop bug-fixes for everyone! github.com/rubocop/rubocop/rel

    Enjoy!

    I also realized we skipped RuboCop 1.83 due to an issue in the release script... Oh, well...

    #ruby

  28. Moar #RuboCop bug-fixes for everyone! github.com/rubocop/rubocop/rel

    Enjoy!

    I also realized we skipped RuboCop 1.83 due to an issue in the release script... Oh, well...

    #ruby