When I started the RCRE project, my initial goal was to implement a JSON-based React component rendering engine to solve some of the non-standard and repetitive problems I faced in the past. This is the origin of the name RCRE(React Component Render Engine).
However, I later found out that the design (automatic state, automatic interface, automatic form) that was used to implement the JSON generated page was highly versatile, and these functions should not be limited to the narrow field of JSON.
Therefore, before I released it, I added support for the pure React component on the existing JSON rendering architecture, which is what everyone is seeing in the documentation.
However, the previously developed JSON rendering features will always be supported, and they share the same implementation.
When I started the RCRE project, my initial goal was to implement a JSON-based React component rendering engine to solve some of the non-standard and repetitive problems I faced in the past. This is the origin of the name RCRE(React Component Render Engine).
However, I later found out that the design (automatic state, automatic interface, automatic form) that was used to implement the JSON generated page was highly versatile, and these functions should not be limited to the narrow field of JSON.
Therefore, before I released it, I added support for the pure React component on the existing JSON rendering architecture, which is what everyone is seeing in the documentation.
However, the previously developed JSON rendering features will always be supported, and they share the same implementation.