Skip to content
New issue

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

Redocly mangles some property names #2541

Closed
DASPRiD opened this issue May 16, 2024 · 3 comments
Closed

Redocly mangles some property names #2541

DASPRiD opened this issue May 16, 2024 · 3 comments

Comments

@DASPRiD
Copy link

DASPRiD commented May 16, 2024

Describe the bug
In some cases it seems like Redocly mangles property names for no apparent reason. In the following OpenAPI spec, the property expiresIn gets displayed as expirese.

Expected behavior
Redocly should not mangle property names.

Minimal reproducible OpenAPI snippet(if possible)

openapi: 3.1.0
info:
  title: Test API
  version: 1.0.0
paths:
  /test:
    get:
      responses:
        "200":
          content:
            application/json:
              schema:
                type: object
                properties:
                  expiresIn:
                    type: integer

Screenshots
image

@DASPRiD
Copy link
Author

DASPRiD commented May 17, 2024

I tracked this down a little bit further, and it seems like the correct name makes it all the way down to React in components/Fields/Field.tsx. So I assume this might be a React bug.

I see that Redocly is stuck on React 17.0.2. Since that is the latest release of that major version, and if this is actually not some configuration issue in Redocly's usage of React, the only way to fix this issue would be to upgrade the React dependency.

Just FYI, the name shows up correctly through the title attribute of the cell, but the name gets mangled as a text node of the span in React's createElement() somehow.

@AlexVarchuk
Copy link
Collaborator

Hi @DASPRiD, I tried to test it, and cannot reproduce it. I have correct field name expiresIn.
Screenshot 2024-05-23 at 12 27 41

Please, provide additional information about reproducing it and we'll try to help you.

@DASPRiD
Copy link
Author

DASPRiD commented May 23, 2024

Oh, I just figured out that one of my browser extensions was at fault, sorry for the noise, closing.

In case anyone else stumbles upon this, this is the extension in question: https://addons.mozilla.org/en-US/firefox/addon/binnen-i-be-gone/

@DASPRiD DASPRiD closed this as completed May 23, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants