We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
solon模块作为整个项目的内核,从我目前比较粗浅的理解来看,可以进行一定的精简,使得项目层次更加容易理解。大概调整逻辑为: 将mvc、router、handle等功能从模块中剥离,solon模块只保留项目配置初始化,生命周期管理,事件传播等功能。
The text was updated successfully, but these errors were encountered:
这里有两个方面:
Sorry, something went wrong.
之前也有很多人这么提过。从技术角度,分开确实更好。从实用角度,真不好说!
这里有两个方面: 从实用角度,现在应该是更好的,而且确实也不大。。。从技术角度,分开更好,显得内核更内核,且结构更清晰。 历史原因,需要向上兼容。。。2.7.0 时 mvc 已经独立出去了,在发包那一刻又合回来了(就是怕造成兼容问题)
理想和现实确实总是有差距的,这个不可避免。。
No branches or pull requests
solon模块作为整个项目的内核,从我目前比较粗浅的理解来看,可以进行一定的精简,使得项目层次更加容易理解。大概调整逻辑为:
将mvc、router、handle等功能从模块中剥离,solon模块只保留项目配置初始化,生命周期管理,事件传播等功能。
The text was updated successfully, but these errors were encountered: