Idea and motivation: @Mohammad-Alavi ❤️

Summary

I propose modifying the apiato:generate:container command to remove the default generated tasks. Instead, developers can directly utilize repository methods within action classes, thereby reducing unnecessary boilerplate and simplifying the codebase.

Motivation

The current implementation of the container generator command creates default tasks, which often results in redundant boilerplate code. By allowing action classes to access repository methods directly, we can streamline the development process and enhance code maintainability. This approach is also in line with the Porto architecture, which does not forbid accessing repositories from actions. Therefore, simplifying the code by removing tasks that duplicate repository logic is both permissible and beneficial.

Proposed Changes

• Modify the apiato:generate:container command to exclude default task generation.
• Update Documentation to reflect the new best practice of using repository methods directly in action classes.
• Ensure Backward Compatibility for existing projects that rely on the current behavior.

Additional Reasons

• Flexibility: The task generator command (apiato:generate:task) will remain available for any use case where tasks are beneficial, providing developers with the flexibility to use tasks as needed.
• Consistency with Sub-Actions: This approach mirrors our handling of sub-actions, which are available but not included by default in generated containers.
• Prevent Misunderstanding: Removing default tasks will prevent new developers from mistakenly assuming that tasks are the mandatory way to call repository methods or that tasks are an essential component of every container.

Implementation Plan

1. Update the Generator Command: Modify the apiato:generate:container command to exclude default tasks.
2. Revise Documentation: Provide updated guidelines and best practices for using repository methods directly in action classes.
3. Offer Examples: Include examples and use cases in the official documentation to illustrate the new approach.
4. Gather Feedback: Solicit community feedback to refine and improve the proposal based on input.

Feedback Request

We value the community's input on this proposal. Specifically, we would like to hear:

• Do you agree with the motivation for this change?
• Are there any potential issues or challenges you foresee?
• Do you have suggestions for improving this proposal?

Thank you for your feedback and support in making Apiato better for everyone!