Change Exception Handling for Non-Existent Components in CBWIRE v4

[grantcopley]

Objective

To update the exception thrown when a non-existent component is called in CBWIRE v4, replacing Injector.InstanceNotFoundException with CBWIREInstanceNotFoundException.

Details

In the current version of CBWIRE (v3), calling a non-existent component results in the system throwing an Injector.InstanceNotFoundException. This needs to be updated in CBWIRE v4 for better clarity and specificity in error handling.

Example Use Case

Consider the following scenario in CBWIRE v3:

#wire( "MyMissingComponent" )#

In this example, when a component named "MissingComponent" (which does not exist) is called, the system throws an Injector.InstanceNotFoundException. The goal is to change this behavior in CBWIRE v4 so that it throws a CBWIREInstanceNotFoundException instead.

Expected Functionality

• In CBWIRE v4, when a user calls a non-existent component, the system should throw a CBWIREInstanceNotFoundException instead of the current Injector.InstanceNotFoundException.
• This change should be applied across all instances where non-existent components are called.
• The new exception (CBWIREInstanceNotFoundException) should be documented in the CBWIRE v4 documentation, including its usage and scenarios where it can be encountered.