現(xiàn)在公司用開發(fā)給前端用的接口，語言是Java，現(xiàn)在想定開發(fā)規(guī)范，然后有些糾結(jié)的地方：
一個是接口的名稱，之前用的的駝峰的形式，比如myTopic，但是看網(wǎng)上推薦的有my_topic，更容易辨識，或者推薦比較多的my-topic，看到說法是比前一種輸入起來更方便。
還有個入?yún)⒌膯栴}，比如一個接口接受的參數(shù)是分頁的頁數(shù)，之前也是習(xí)慣性的駝峰的pageNum，但看很多公司，比如支付寶的接受參數(shù)都是page_num這種。
想問下大家以上兩個問題一般用的是那種或推薦哪種？
5
0
0
認(rèn)證0級講師
Each company has different writing methods, and even different teams within a company will have different writing methods.
But there is always a way of writing that is correct most of the time, and that is the hump.
The camel case writing method has also been verified by experiments. It is the easiest to recognize and the recognition speed is fast. You can read the study on camelback readability here
Personally, I think the so-called specification is the agreement between your front-end and backend. Once the agreement is made and it can meet the needs, then this agreement is your specification.
There is no standard answer to the style question. Cases can be found in the 3 methods you listed.
I personally use the underline method page_num, which is more readable and uses lowercase letters, which is more suitable for url/uri.
It is recommended to use Douban’s URL design http://www.prower.cn/interact...
![[Web front-end] Node.js quick start](https://img.php.cn/upload/course/000/000/067/662b5d34ba7c0227.png)
