-
Notifications
You must be signed in to change notification settings - Fork 3
Description
Description
What needs to be done?
After completing the changes described in issue https://github.com/RonasIT/laravel-entity-generator/issues/178 , refactor the code base to stop using RonasIT\Support\Exceptions\ClassAlreadyExistsException. Instead, all places where this exception is currently thrown should be updated to throw ResourceAlreadyExistsException directly without throwFailureException method usage.
Expected Outcome
What is the expected result?
No usage of
ClassAlreadyExistsExceptionremains in the code.All exception throwing related to existing resources explicitly throws
ResourceAlreadyExistsException.The method
throwFailureExceptionis no longer used anywhere for this purpose.The code remains clean, follows good exception handling practices, and is consistent with the changes introduced by issue Implement ResourceAlreadyExistsException #178.