strapi-plugin-documentation generates "foo" response

[badsyntax]

Bug report

Describe the bug

I'm seeing the following response body definition for my single content type:

"responses": {
    "200": {
    "description": "Retrieve about-page document(s)",
    "content": {
        "application/json": {
          "schema": {
            "properties": {
              "foo": {
                 "type": "string"
              }
            }
          }
        }
    }
},

Steps to reproduce the behavior

1. Create a single content type with spaces in the Display name. The generated UID should contain dashes - this is the important part that triggers the bug
2. View the generate OpenAPI spec

Expected behavior

I would expect the generated openapi spec to be:

"responses": {
    "200": {
    "description": "Retrieve about-page document(s)",
    "content": {
        "application/json": {
        "schema": {
            "type": "array",
            "items": {
            "$ref": "#/components/schemas/AboutPage"
            }
        }
        }
    }
},

System

• Node.js version: v14.15.5
• NPM version:6.14.11
• Strapi version: 3.6.3
• Database:postgres
• Operating system: macos

[badsyntax]

The problem is the usage of lodash _.lowerCase. Have a look at the docs: https://lodash.com/docs/4.17.15#lowerCase

It's converting aaa-aa to aaa aa and thus this conditional check is failing:

strapi/packages/strapi-plugin-documentation/services/Documentation.js

Line 1160 in aebdb33

isModelRelated = strapi.models[tag] !== undefined && tag === _.lowerCase(controller);

which results in 'aaa-aa' === 'aaa aa'

[derrickmehaffy]

This issue has been mentioned on Strapi Community Forum. There might be relevant details there:

https://forum.strapi.io/t/strapi-breaks-when-using-hyphens-in-content-type-uid-names/5865/1

[badsyntax]

@derrickmehaffy Yes I just created that forum post. Is this an automated message? (It's not clear.)

[derrickmehaffy]

@derrickmehaffy Yes I just created that forum post. Is this an automated message? (It's not clear.)

Yes this is an automated message.

[github-actions]

Hello!

As we have not received any new or updated information to reproduce this issue in the last 14 days we are marking this issue as closed. Should you have new information please feel free to respond and we will consider reopening it.

If anyone else have updated information for this issue, please open up a new bug report and simply reference this closed bug report so that we can get any new information you may have. If you have questions please refer to the contributor's guide on opening issues.

Thank you and have a great day!