Allow to as method parameter in default config

[unused]

Add to to AllowedNames in default configuration for cop
Naming/UncommunicativeMethodParamName in order to allow common
methods handling date ranges with parameter set_date_range(from, to)

[koic]

Please write the link to this PR at the beginning 😃

- * Change `Naming/UncommunicativeMethodParamName` add `to` to allowed names in default config. ([@unused][])
+ * [#5626](https://github.com/bbatsov/rubocop/pull/5626): Change `Naming/UncommunicativeMethodParamName` add `to` to allowed names in default config. ([@unused][])

[unused]

sorry and thx 😄

[Drenmi]

Would it be meaningful to add some common preposition, such as "in", "on", "at", etc.?

[bbatsov]

Perhaps, although I've rarely seen those as method names.

[pocke]

Would it be meaningful to add some common preposition, such as "in", "on", "at", etc.?

Yeah, but in is keyword of Ruby (for var in collection syntax) so we cannot use in as method parameter name.

[pocke]

Can you check the failing build on Travis CI?
https://travis-ci.org/bbatsov/rubocop/jobs/349272326#L1387-L1388
Probably we should fix the document generator task. Probably it seems confusing with an empty value.

[unused]

I cannot think of an example using "in", "on", "at" except using some as pre-/suffixes. Happy to add if someone provides a legit code example :)

[unused]

I manually adapted the documentation, did not know about the generation task - did I miss it in the contribution guide? If it is missing, it might be a good hint to have.

[bbatsov]

It's in the PR template, but probably you didn't notice it there.

Can you rebase on top of master?

[unused]

Thx, I'll double check next time.

Rebased.

[deivid-rodriguez]

What about ip? Can we get that added too?

[bbatsov]

Sure.