Github.com/jianliaoim/…
My friend heard some wind and saw it on GitHub. It has both front and back ends. It should be able to run locally. My resignation was announced by uncle Migrant workers. In fact, I have been recuperating at home for more than half a month. My cough is much better, but it is easy to relapse
The overall plan of the front end is based on one-way data flow, Store and debugging tools implemented by ourselves. There is no problem with this part. The interface rendering adopts component nesting, continues immutable data, and designs routing by itself. ListenTo was left by early Backbone, so there was no time to clear it all. The data synchronization part was unified by Actions, and the Actions in didMount were also deleted as far as possible. In the Restful request part, the data-rely scheme is designed to batch capture data, which is not perfect. I think there is no problem. The action distribution code exists in handler/ actions/ two files. The unpackaged Gulp Webpack with scripts to deal with multiple environments was basically adequate for Modal and Popover components before the react-stack-Modal components were designed but abandoned in half
On the whole, a lot of modifications were made in the early stage to correct the remaining problems of Backbone and improve the development efficiency, but some problems occurred when the code was switched to Immutable Data, which resulted in few conditions for further improvement. In the past two years, I spent a lot of energy thinking about how to achieve 1. Fast development, 2. Robust data flow and never expected to be presented this way. Anyway, if you look at the code please be careful not to be misled by the compromise code and the internal decisions that are being made in the company I don’t know, as soon as they release the information, but I think they will add some clarification