FIX description field (required) may be null

[soranoba]

Now, description fields are often null, but it is required.
I fixed it become the correct format by changing to empty character from null.

        "responses": {
          "201": {
-            "description": null,
+            "description": "",
            "schema": {
              "$ref": "#/definitions/HogeEntity"
            }
          }
        },

"definitions": {
    "HogeEntity": {
      "type": "object",
      "properties": {
         "id": {
          "type": "integer",
          "format": "int32",
          "description": ""
        }
     },
     "required": [
        "id"
      ],
-      "description": null
+      "description": ""
    }

This is caused by omitted of detail or message.
However, these are I/F assuming that they can be omitted.

# detail omitted
post failure: [
    {code: 201, model: Entities::HogeEntity} # message omitted
] do
  status 201
end

[grape-bot]

	1 Warning
⚠️	There’re library changes, but not tests. That’s OK as long as you’re refactoring existing code.

Generated by 🚫 danger

[coveralls]

Coverage decreased (-0.1%) to 97.798% when pulling d9537e9 on soranoba:fix/description_may_be_null into 1d14091 on ruby-grape:master.

[coveralls]

Coverage increased (+1.7%) to 99.645% when pulling c35f03d on soranoba:fix/description_may_be_null into 1d14091 on ruby-grape:master.

[coveralls]

Coverage decreased (-0.1%) to 97.798% when pulling c35f03d on soranoba:fix/description_may_be_null into 1d14091 on ruby-grape:master.

[LeFnord]

please proveide a spec to document the fix … thanks

[soranoba]

@LeFnord

The description of this PR changed.
Please let me know if there is still a shortage.

[LeFnord]

thanks @soranoba … now it is clear 😄