CompletionCommand does not need to know about custom application-level options
in user code. This filters out options that aren't in the default set provided
by the base Application class to prevent conflicts with option names.
If user-code wants to use global options in a subclass of CompletionCommand,
filterApplicationOptions can be overridden to append any desired options to
the default list.
Resolves the issue from #86 in a backwards compatible way.
CompletionCommand
does not need to know about custom application-level options in user code. This filters out options that aren't in the default set provided by the baseApplication
class to prevent conflicts with option names.If user-code wants to use global options in a subclass of CompletionCommand,
filterApplicationOptions
can be overridden to append any desired options to the default list.Resolves the issue from #86 in a backwards compatible way.