Fix method order in the Mixin Grouping section

[ydakuka]

See rubocop/rubocop#12321 (comment)

[pirj]

The rubocop repo comment says we should not change the order to avoid behaviour change.

Here, we also shouldn’t create an impression that we insist on alphabetical or any ordering.
And the Bar, Foo order feels extremely unnatural and no doubt steals focus from the guideline in question.

I don’t think it makes sense to introduce a rule to sort includes. It would be a nightmare to have all exceptions marked with rubocop:disable.

[ydakuka]

The rubocop repo comment says we should not change the order to avoid behaviour change.

Ok, should the PR (#924) be reverted?

[pirj]

No. Kwargs ordering had a clear inconsistency ‘bar’ was a required kwarg as specified in the “bad” example. It should have remained such in the ‘good’ example. This has nothing to do with alphabetic ordering of kwargs.

In any case, kwargs ordering change is cosmetic, while module inclusion order change can cause behaviour change.
Having a alphabetic order is in some cases impossible, and would force users to face hard to track bugs, and in the end inline disable the cop for certain order-sensitive includes.

I’ll close this unless the community has a strong preference for alphabetic order

[ydakuka]

Got it, thanks for the explanation.