Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

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

Jump to bottom

[Feature Request]: 项目结构调整讨论 #244

Open
4o3F opened this issue Nov 1, 2022 · 5 comments
Open

[Feature Request]: 项目结构调整讨论 #244

4o3F opened this issue Nov 1, 2022 · 5 comments
Labels
enhancement New feature request

Comments

@4o3F
Copy link

4o3F commented Nov 1, 2022

个人见解，Web后端重要的在于向外暴露的API和自身数据处理储存，因而有以下一些建议
我个人经验也不十分充足，还请各位大佬多提意见和修改

  • 将所有
    • API相关的(狭义上包括Handler, Middleware,等)
    • 数据库处理相关的(狭义上包括直接操作数据库的GORM相关,MeliSearch相关)

以及其他同等级别的都放在同一级目录下，取代目前的web和其他组件放于同一级下的结构

  • ...
    仅为初步构思，还望各位积极补充，有新的想法了我也会更新该issue
@4o3F 4o3F added the enhancement New feature request label Nov 1, 2022
@trim21
Copy link
Contributor

trim21 commented Dec 29, 2022 •
edited

golang 不支持循环导入，处理起来太麻烦了...

比如 subject type或者episode type应该放到subject/episode包里，但是因为无法循环导入的问题，这些都只能放到model里...

@trim21
Copy link
Contributor

trim21 commented Jan 2, 2023

拆微服务了!

@mrokoo
Copy link

mrokoo commented Jul 3, 2023

感觉根目录下出现packagejson就很难受，现在再搞微服务了？

@trim21
Copy link
Contributor

trim21 commented Jul 4, 2023

放在子目录的话用起来很难受

@trim21
Copy link
Contributor

trim21 commented Jul 4, 2023

起码时间线部分是拆出去了

@trim21 trim21 closed this as completed Jul 4, 2023
@trim21 trim21 reopened this Jul 4, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
enhancement New feature request
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@trim21 @4o3F @mrokoo