<-- 如果你也想知道答案,请在左侧点个顶,谢谢。
I'm going to use Reactjs to do the V-level work and laravel to do the C and M work. Is this method feasible? Is there any need for this?
In addition, for example login, how blade should be translated into Reactjs's component code, or how can I replace Laravel's front-end template with Reactjs:
Are there any related project codes that can be referenced by wood? Thanks for sharing
Reply content:
<-- 如果你也想知道答案,请在左侧点个顶,谢谢。
I'm going to use Reactjs to do the V-level work and laravel to do the C and M work. Is this method feasible? Is there any need for this?
In addition, for example login, how blade should be translated into Reactjs's component code, or how can I replace Laravel's front-end template with Reactjs:
Are there any related project codes that can be referenced by wood? Thanks for sharing
First, it's usually called react.js instead of Reactjs.
To get the most out of react.js, I would suggest a complete separation of the front and back end, only through JSON communication. Instead of using Laravel to output the front-end code
Front end with React-router made isomorphic Web-app, specific code and tutorials can refer to my first answer on SF
The backend only uses Laravel's RESTful API-related parts, the main logic is written in the M layer, the Controller almost no need to write code
Phone code word inconvenience, have time to perfect
You can refer to this React-laravel