Describe the bug
Giving an invalid home command sometimes throws the generic BadCommandException instead of one with the specific invalid home command message that's introduced in #125.
To Reproduce
One method to reproduce the behavior:
Issue hb command
Issue home --Test, which throws the specific invalid home command message introduced in #125
Issue home Test, which now throws the generic BadCommandException message from MainManager
User was taken back to MainManager already, even though home Test is not a valid home command
Another method to reproduce the behavior:
Issue hb command
Issue home Test, which throws the specific invalid home command message introduced in #125
Issue home --Test, which now throws the generic BadCommandException message from MainManager
User was taken back to MainManager already, even though home Test is not a valid home command
Expected behavior
Step 3 in both test cases above should give user the specific invalid home command message introduced in #125, and user should not be taken back to MainManager.
Describe the bug Giving an invalid
home
command sometimes throws the generic BadCommandException instead of one with the specific invalid home command message that's introduced in #125.To Reproduce One method to reproduce the behavior:
hb
commandhome --Test
, which throws the specific invalid home command message introduced in #125home Test
, which now throws the generic BadCommandException message fromMainManager
MainManager
already, even thoughhome Test
is not a valid home commandAnother method to reproduce the behavior:
hb
commandhome Test
, which throws the specific invalid home command message introduced in #125home --Test
, which now throws the generic BadCommandException message fromMainManager
MainManager
already, even thoughhome Test
is not a valid home commandExpected behavior Step 3 in both test cases above should give user the specific invalid home command message introduced in #125, and user should not be taken back to
MainManager
.