preface
Front-end self-study party, because of love, so unswervingly, love code, love to rush about in different business. At present the senior, looking for the internship, have the way of seniors feel that you can, you can give younger brother inside push.
This project is based on the React family bucket, and all data are simulated using Mock+ JSON.
For project construction, in order to facilitate later maintenance, I personally think we should adopt a divide-and-conquer idea to manage different modules, such as API and Components…… And so on. In the process of component coding, it is also necessary to divide module management, module separation and code segmentation. Once the business is complex, the code will appear particularly bloated, so it is still necessary.
Some development experience, I think, should be presented in the form of issue, under the warehouse, and then add appropriate label for the corresponding issue. It is also a good choice to consolidate and review later for problem solving and experience recording of project development. After all, experience is divided into different business scenarios.
The message of a commit record should be separated by: verb: action content. There are some good framework commit records that do this, and I personally think it’s worth learning from.
Project directory
Github submission management
Record experiences and problems
Some examples:
conclusion
This is what I do for the benefit of development, version control, and post-maintenance of a complete project during development and refinement. Of course, this is just my personal approach.
Newbie on the road, learn React, hope more advice.
The project address
Project address: Click me direct