Changed IConfigurator to return IConfigurator instead of void

[byte2pixel]

Fixes #1219

• I have read the Contribution Guidelines
• I have commented on the issue above and discussed the intended changes
  • the discussion was on an issue and was discussed with @FrankRay78 CommandAppTester overrides console #1713 (reply in thread)
• A maintainer has signed off on the changes and the issue was assigned to me
  • see above link to discussion.
• All newly added code is adequately covered by tests
• All existing tests are still running without errors
• The documentation was modified to reflect the changes OR no documentation changes are required.

Changes

Changed IConfigurator to return IConfigurator instead of void for the following interface methods:

• SetHelpProvider
• SetHelpProvider<T>
• AddExample

However, other methods like AddCommand narrow the configurator so the order of chaining methods does matter. Just to point that out. Chaining is optional obviously.

I saw the ICofiguratorOfT also returns void for SetDescription, and AddExample. However, it becomes a bigger challenge to change that because Configurator<T> implements both IUnsafeBranchConfigurator and IConfigurator<T> and both share the SetDescription and AddExample but one does not take in the generic type. Probably would need "unsafe configurator of T" or something?

---

Please upvote 👍 this pull request if you are interested in it.

[FrankRay78]

Thanks, I'll review this shortly.

[FrankRay78]

Many thanks @byte2pixel, much appreciated and welcome to the git commit history.

[byte2pixel]

Many thanks @byte2pixel, much appreciated and welcome to the git commit history.

@FrankRay78 Thanks, hopefully more to come. Hitting a busy patch at work with adding an embedded db to an application.