Mediating style discussions is hard.
Past discussion was mostly passive
Seems they've added it before I've made a correction to the article basing on your lexical scope remark.
@james You're right, the wording it's defined in top-level namespace is incorrect, should be the same scope as the block containing it. 👍
@james Couldn't find a better answer than this https://github.com/rspec/rspec-core/issues/2181#issuecomment-190535022
Question. In which namespace `B` is defined?
A = Class.new do
B = 1
A::B # => ???
B # => ???
More on the topic https://fili.pp.ru/leaky-constants.html
@james There's a cop for that™
Are you adventurous enough to use Sidekiq via ActiveJob?
Would you like to hear a success story with a lot of "gotcha" moments?
Would you be interested in seeing a list of best practices digested from over a hundred of background job related code reviews?
Fresh article about an adventure in which I'm fixing a single cop, check it out:
@ioquatix There's a good explanation why it should go to stderr in "A Research UNIX Reader: Annotated Excerpts from the Programmer’s Manual":
Let's improve thread creation in Ruby by an order of magnitude: https://github.com/ruby/ruby/pull/2227 😍
Posted an article about Open Source, Biochemistry, and Happiness.
Appreciate your feedback.
Posted a small article on Toreman, one-line `Procfile` manager
Converted the Rails style guide and the Ruby style guide to AsciiDoc, too.
Why AsciiDoc? It's hard to write a blog post. It's easy to write an email. AsciiDoc was created to be easy to write in the first place.
Pushed Toreman (https://github.com/pirj/toreman), a one line of shell script Foreman port for tmux.
Went through the open tickets in `rubocop-rspec`, fixed three bugs, added (well, extracted) a new cop.
Did you know that if you declare a constant or a class inside RSpec's DSL, they will be declared globally, and will clash with subsequent declarations?
Vote for it! https://github.com/rubocop-hq/rubocop-rspec/pull/765