REST API: ReflectionException "Class 'Webkul\Attribute\Http\Requests\AttributeForm' does not exist" in Krayin CRM v2.0.1

[fitulka]

Description:

After integrating the REST API package (commit 121c25b) with Krayin CRM v2.0.1, I encountered an error when attempting to create contacts via API endpoints. The issue specifically occurs when making POST requests to the following endpoints:

/api/v1/contacts/organizations
/api/v1/contacts/persons

The system throws a ReflectionException stating that the class Webkul\Attribute\Http\Requests\AttributeForm does not exist.

Request Example (for /api/v1/contacts/persons):

curl -X 'POST'
'https://crm.example.com/api/v1/contacts/persons'
-H 'accept: application/json'
-H 'Authorization: Bearer 1|HznFUL2xut1UpxjGcQM8cDW3NjJiRgfjRDUYrvJYe48fb0a2'
-H 'Content-Type: application/json'
-H 'X-CSRF-TOKEN: '
-d '{
"name": "John Doe",
"emails": [
{
"value": "[email protected]",
"label": "work"
}
],
"contact_numbers": [
{
"value": "09315981404",
"label": "work"
}
],
"organization_id": 1,
"entity_type": "persons"
}'

Response:

{
"message": "Class 'Webkul\\Attribute\\Http\\Requests\\AttributeForm' does not exist",
"exception": "ReflectionException",
"file": "/var/www/htdocs/example.com/crm/vendor/laravel/framework/src/Illuminate/Routing/ResolvesRouteDependencies.php",
"line": 81,
"trace": [...]
}

Steps to Reproduce:

1. Install Krayin CRM v2.0.1.
2. Install the latest commit (121c25b) of the REST API package.
3. Try creating a new contact via the /api/v1/contacts/persons or /api/v1/contacts/organizations endpoint.

The error occurs during the request, and the contact is not created.

Expected Behavior:

The API should correctly handle the request and create the contact as expected.

Environment:

Krayin CRM v2.0.1
REST API Package Commit 121c25b
PHP 8.2.x

Additional Context:

It seems the Webkul\Attribute\Http\Requests\AttributeForm class might be missing or not properly registered within the application. Since the REST API relies on core functionality in Krayin CRM, it's unclear if this issue is related more to the CRM codebase or the API package.

We are currently evaluating whether to stay on version 2.0.1 or revert to 1.3.0 to ensure full API functionality.

Could you provide clarification or guidance on this issue?

[suraj-webkul]

This issue has been fixed in this PR.