Fix #689 - Fixed invalid import of ItemNotFoundException #690
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
Replaced all incorrect occurrences of:
use ApiPlatform\Core\Exception\ItemNotFoundException;with the correct:
use ApiPlatform\Exception\ItemNotFoundException;The wrong namespace caused ItemNotFoundException to be thrown when registering multiple Process Handlers for the same module (e.g., Leads). This fix ensures correct exception handling and consistent imports.
Motivation and Context
The incorrect import prevented the invocation of a second Process Handler in the Leads module and potentially other modules, despite the getProcessType() method being called. Correcting the namespace resolves the error and restores expected functionality.
How To Test This
Create a Process Handler for the Leads module (e.g., record-lead-update-status).
Verify it registers successfully.
Create a second Process Handler for the Leads module (e.g., record-lead-update-next-steps).
Before fix: second handler fails with ItemNotFoundException.
After fix: both handlers register and work as expected.
Types of changes
Final checklist