Skip to content

Conversation

@callyall
Copy link

@callyall callyall commented Apr 5, 2024

  • Updated inaccurate and added missing docblocks
  • Simplified the overall structure
  • Deprecated the "with" methods

- Updated inaccurate and added missing docblocks
- Simplified the overall structure
- Deprecated the "with" methods

public function __construct(Module $module)
/** @param Array<ProcedureRoute>|Generator<ProcedureRoute> $_routes */
public function __construct(protected array|Generator $_routes)
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This should stay as module, otherwise its a breaking change.

Copy link
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looking at the code base this looks like an object that is used internally and I've already updated the reference(https://github.com/cubex/api-foundation/pull/4/files#diff-d08ab29dc7d96cd6c5d5f15f1c75366b9f4167b82a94951330adda2d7bac1ec6R30)?

* @param int $code
* @param Throwable|null $previous
*/
public function __construct(string $type, string $message = "", int $code = 0, ?Throwable $previous = null)
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This doesn't follow the constructor for Exception

Copy link
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

As we are looking to add a type I don't see why we want it to follow the exception constructor.

{
$payload->fromContext($c);
}
throw new Exception("Unable to handle procedure: execute missing");
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The response code is lost here

Copy link
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Fixed

return JsonResponse::create($response);
if (!$plClass)
{
return JsonResponse::create($procedure->execute());
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We should avoid creating the JsonResponse twice here.

Its preferred to create the final response in a single line for improved refactoring or modification in the future.

Another option to would be to have a method to convert the response to the JsonResponse. This would give us the option to return as text/xml for different clients, or endpoints.

Copy link
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Having an else statement increases code complexity. An early return does look like the better option here.

If we need to modify any of this logic we can override the method.

public function complete(Context $context)
{
$context->meta()->set('api.module', get_class($this->_module));
$context->meta()->set('api.module', $this->_moduleClassName);
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

As class names are not case sensitive, sticking with get_class here is safer

Copy link
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Fixed

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants