Q: 能不能URL规则点 || Q: Can URL rules point

[hulang]

Describe the bug | 问题描述

https://waline.js.org/reference/server/api.html
能不能URL规则点：
GET /api/comment/list 列表
POST /api/comment/insert 添加
POST /api/comment/update 编辑
POST /api/comment/like 点赞
POST /api/comment/status 通过/审核/垃圾
POST /api/comment/sticky 置顶
怎么实现这样，后端代码总是在一个comment方法里面写判断，代码写的稀烂，我想在comment控制器里面，定义各种方法。。这样结构清晰。

Website URL | 问题网站

https://waline.js.org/reference/server/api.html

Where your waline deploy? | 服务部署在哪里？

Vercel (Default)

Where your comment data store? | 数据存储在哪里？

LeanCloud(https://leancloud.app)

---

Describe the bug | Problem description

https://waline.js.org/reference/server/api.html
Can you point to URL rules:
GET /api/comment/list list
POST /api/comment/insert add
POST /api/comment/updateEdit
POST /api/comment/like like
POST /api/comment/status pass/review/trash
POST /api/comment/sticky sticky
How to achieve this, the back-end code always writes judgments in a comment method, the code is poorly written, I want to define various methods in the comment controller. . This structure is clear.

Website URL | Problem Website

https://waline.js.org/reference/server/api.html

Where your waline deploy? | Where is the service deployed?

Vercel (Default)

Where your comment data store? | Where is your comment data store?

LeanCloud (https://leancloud.app)

[lizheming]

Waline API 是基于 RESTful API 语义的，除了 GET /api/comment 评论列表那块因为耦合了最近评论和前台评论列表以及后台评论列表的操作，用 type 区分没有做很好的拆分有点恶心之外，我觉得 POST /api/comment 和 PUT /api/comment 的实现还是很好的，没什么问题的。

基于功能语义的 API 确实能让每个功能更好的拆分，但它不好的地方在于会写非常多的重复代码。比如你列举的这几个 API，其实本质就是去修改 comment 表的某个字段，但如果拆分4个控制器的话，这个同样的数据库操作你就要写四遍。

POST /api/comment/update 编辑
POST /api/comment/like 点赞
POST /api/comment/status 通过/审核/垃圾
POST /api/comment/sticky 置顶

Waline API 的 RESTful 语义不算特别完美，但也不至于稀烂~ 你可以先说下你要做什么以及你的诉求，我看下怎么组织处理会比较好？

---

Waline API is based on RESTful API semantics, except for GET /api/comment comment list, because it is coupled with recent comments, foreground comment list and background comment list operations, it is a bit disgusting to use type to distinguish without doing a good split In addition, I think the implementation of POST /api/comment and PUT /api/comment is still very good, there is no problem.

The API based on functional semantics can indeed make each function better split, but its disadvantage is that it will write a lot of repetitive code. For example, the APIs you listed are actually to modify a certain field in the comment table, but if you split the four controllers, you have to write the same database operation four times.

POST /api/comment/update edit
POST /api/comment/like Like
POST /api/comment/status pass/review/trash
POST /api/comment/sticky sticky

The RESTful semantics of the Waline API are not particularly perfect, but they are not rotten~ You can first talk about what you want to do and your demands, and let me see how to organize and handle it better?

[Mister-Hope]

I agree with hulang's opinion that leaving lang as url params with methods that have body (e.g.: post) could be confusing.

We can just redesign the whole api system while adding these new api in v1.

BTW, the @v2 version range in CDN is there in docs since v2 initial release, so we can expect no one will accidentally upgrade to v3 client once it touches stable.

[lizheming]

@hulang 你这一系列问题我看不懂，我只能回答第一个问题，是你不理解 RESTful URL

---

@hulang I can't understand your series of questions, I can only answer the first question, you don't understand RESTful URL

[lizheming]

@Mister-Hope 我没有理解你的问题，我认为 POST 请求有 GET 参数是一个很正常的事情。

---

@Mister-Hope I didn't understand your question, I think it's a very normal thing for POST request to have GET parameters.

[hulang]

@Mister-Hope 我没有理解你的问题，我认为 POST 请求有 GET 参数是一个很正常的事情。

@Mister-Hope I didn't understand your question, I think it's a very normal thing for POST request to have GET parameters.

POST 请求有 GET 参数是一个很正常的事情，我笑了哈，，从来没有见过阿里云，百度，他们提供API接口的，还有POST里面带GET的。。

[lizheming]

@hulang 你没见过并不一定是错误的，我没有时间去找一个例子给你去验证这个事情，后续找到的话我给你发一下 在 GitHub 和你一直在提的百度随便找了两个 API 给你你可以一下，既有 Body 参数又有 URL 参数的。另外，我已经是非常客气的在和你沟通了，在我看来你确实不知道的东西有很多，我也并没有高高在上的和你沟通。如果你一直是这种阴阳怪气的语气沟通的话，后续的评论我就不回了。Waline 项目本身反正也是开源的，你可以按照你的需要随便改。

• https://docs.github.com/en/rest/repos/contents?apiVersion=2022-11-28#create-or-update-file-contents
• https://cloud.baidu.com/doc/BOS/s/zkc5ne644

---

@hulang It’s not necessarily wrong that you haven’t seen it. ~~ I don’t have time to find an example for you to verify this matter. If I find it later, I will send it to you~~ Find it on GitHub and Baidu you have been mentioning There are two APIs for you, you can look at it, there are both Body parameters and URL parameters. In addition, I have communicated with you very politely. In my opinion, there are many things that you really don't know, and I have not communicated with you in a superior manner. If you have always communicated in this yin and yang tone, I will not reply to the follow-up comments. The Waline project itself is open source anyway, and you can change it to suit your needs.

• https://docs.github.com/en/rest/repos/contents?apiVersion=2022-11-28#create-or-update-file-contents
• https://cloud.baidu.com/doc/BOS/s/zkc5ne644