use default assignee only if category is not specified or it doesn't have a default assignee itself

[piccio]

#30
use default assignee only if category is not specified or it doesn't have a default assignee itself

[giddie]

Thanks for doing this work :)

[giddie]

Just wondering why the indentation has changed here? Looks like it might have gained a space?

[piccio]

I think that 2 spaces indentation is a ruby best practice
https://github.com/bbatsov/ruby-style-guide#source-code-layout

[giddie]

Oh, was there only 1 previously? If so, could you re-indent the whole file a separate commit, so that the code changes don't get lost in the whitespace change?

[piccio]

no I'm sorry I'm hurry

[giddie]

OK, I've tested this, and I'm quite confused: for me, in non-interactive mode, the category assignee is set before #assign_default_assignee is called, and because an assignee is already set, it returns early. So in non-interactive mode, the plugin already has no effect by default. Is this pull request intended to enable the plugin to forcibly override the default specified by the category on issue creation? (If so, I think that would be of limited use: you could simply remove the category default assignee instead.)

Can you explain what the desired behaviour is in interactive mode?

[piccio]

sorry reset all
I were working on an old version where the default assignee override the category's assignee.
In the last version this beaviour doesn't occour.