Issue 3916

[sinkcup]

Fixes #3916 Fixes #2327

[emptynick]

Same as #3912

Pull requests should have descriptive titles and ideally a description of what is being fixed and why (the why can include a link back to the original issue). What you've created here is useless to us without more info

[sinkcup]

DRY: do not repeat yourself.

pull request should write nothing, but bind a issue, all description are in the issue.

[fletch3555]

DRY refers to code, not pull requests. If a project maintainer requests you do something a certain way on their project, you should probably do it.

Adding a description makes our lives easier. We're not asking for a 200-slide presentation on how your 2-line change works, but a "x is broken, so this fixes it by doing y instead" would be enough

[sinkcup]

#3916 is broken, I have fixed it.

is it OK? everything need follow DRY.

look at larapack/hooks#41 , A good project maintainer should never break standard.