产品中的原型 定义的 提示文字 是这样的 ：
。。。
PHP 接口提示 文字是这样的
前端调用接口时， 说白了为了偷个懒， 直接把非正常奖品文字 给alert() 出来了， 但是 这提示文字，跟产品定义的提示文字不相符，
所以就造成了问责。 PHP 不改， 说她的提示文字 是给 调用接口的人看的， 然后 雷就到 前端 我这里来了。
本人表示 不服，就想问下， 如果提示有20个 我是不是也要写20个code 判断 丢出 自己定义的文字
伊谢尔伦2017-04-17 16:31:06
There is no problem with the back-end. The front-end prompts and the back-end prompts are different. The prompts written by the back-end tell the front-end why, and the prompts written by the front-end tell the users why.
Besides, what’s the point of spending hours arguing about something that can be changed in 5 minutes?
巴扎黑2017-04-17 16:31:06
Yes, I think the front-end should divide the numbers on the left into 3 categories based on the text on the right, corresponding to the three situations given by the product, and then judge the numbers and display different prompts.
Because the status determined by PHP cannot only be these three types of products, all the statuses are returned to the front end for judgment. If the product adds another status later, it can be easily implemented.
阿神2017-04-17 16:31:06
The specific responsibility lies with the project manager. This is basically a problem at the demand communication level rather than at the technical level
黄舟2017-04-17 16:31:06
Generally speaking, this kind of modification is done by the front end. Fortunately, PHP is a scripting language. If it is a compiled language like C#, the cost of background updates will be greater.
Just a few status codes, just write a switch case and you’re done. Don’t be angry~
大家讲道理2017-04-17 16:31:06
Resolve emotions first, then deal with problems. Even if you get 50 answers supporting you in the forum, what's the point? It is better to write the code first, solve the problem, and then look back to see if there are any communication problems. Otherwise, the progress is stuck here. Who do you think is responsible?
PHP中文网2017-04-17 16:31:06
This kind of responsibility is difficult to explain clearly. It is probably a problem with the product and poor communication.
To put it bluntly in the company, whoever is strong will listen to whoever is strong.
You can make the backend listen to you, or change the backend to listen to the product. , then you don’t need to change the front-end. If you can’t, let you change the front-end now, then just change it.
This kind of problem will be encountered in many cases. Either the front-end is modified or the back-end is modified. It depends on the person to deal with it