Response result definition specific error code

Generally speaking , We define a uniform return result set object , Most will be defined as follows ：

At least many of my previous projects only defined the above attributes , It seems to be enough .

If the above code The return value of the status code defines the sum http There's no difference in response codes , So to be honest , It's hard to tell what's wrong , For example, a very rough handle code The status code is defined as 200 and 500, Success is 200, The error is 500, It may be OK to use it in the short term , The front end can also judge according to these two status codes , However, if it is necessary to provide open interfaces for other projects in the later stage , This definition is not accurate , Too broad a status code , It will make it difficult for users to handle our open interface in line with their own business . After all, errors return 500, If you want the prompt to be accurate , The user can directly throw out the error and exception information of the remote calling interface , But this is tantamount to giving the user experience to the perfection of the third-party interface , Normally , We should allow users to distinguish different exceptions through status codes , The status code corresponding to each case should be different , We should also maintain the corresponding information document of the status code , In this way, users can connect according to their own business conditions , Judge what is wrong according to the status code , Then further encapsulate the error or throw it directly .

In fact, the above code Attribute can be used as specific status code and corresponding to exception information , It just depends on whether we use it well , Whether the status code is defined in detail .

PS： This time just share and record your thoughts , At the same time, it is suggested to define the status code completely at the beginning of the project , Don't throw everything away 500, The finer the definition , In fact, the lower the coupling , Users are also more assured when docking .