Conclusion

The decision about whether or not to use annotations in a software lies with the developer. The decision to remove it from the core of Laravel, as well as the HTML forms packages, shows that the framework is becoming more and more flexible, having as default only a minimum set of packages. This allows for stability and less maintenance for the core developers as Laravel moves towards a long-term-support (LTS) release with Laravel 5.1.

Since the annotations package is part of the Laravel Collective, support for this package will be managed by the team, which guarantees that the feature's usefulness will be extended and expanded with contributions through to the repository.

Also, the package could be extended to include a template that is automatically created with the route annotation that has the same name as the controller. This would save yet another step in the process of creating a controller and route—one of the most essential yet monotonous tasks in the software development process.

..................Content has been hidden....................

You can't read the all page of ebook, please click here login for view all page.
Reset