We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
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
In the case of an error, since the JSON format is not fixed, it is difficult to use for the client. ex.
/communities
{ "description": [ "を入力してください" ] }
/communities/0
{"status":404,"error":"Not Found"}
I considered the following format. What do you think.
{ "level": 1,#1=warning, 2=error "messages": [] #I am considering entering multiple messages. }
The text was updated successfully, but these errors were encountered:
I thought case 1 corresponds to level 1(warning) and case 2 corresponds to level 2(error), is that correct? If possible, I think the format of RFC 7807 is worthy of consideration. https://www.eisbahn.jp/yoichiro/2017/01/rfc_7807.html
Sorry, something went wrong.
@chimame @ytorii これはどうなるの?
これは置いておいてもらっていいですか?
はーい
No branches or pull requests
Problems and suggestions:問題・課題点/提案
In the case of an error, since the JSON format is not fixed, it is difficult to use for the client.
ex.
/communities
./communities/0
.Countermeasure:対応方法(案)
I considered the following format. What do you think.
The text was updated successfully, but these errors were encountered: