fix(transform): avoid duplicate enum declaration when using root types with no prefix

[Newbie012]

Changes

given the following settings:

enum: true,
rootTypes: true,
rootTypesNoSchemaPrefix: true

the generated output will declare an enum and a type with the same name. This PR will avoid redeclaring a type if its node is an enum.

How to Review

The PR is quite minimal - code adjustment + a test

Checklist

• Unit tests updated
• docs/ updated (if necessary)
• pnpm run update:examples run (only applicable for openapi-typescript)

[netlify]

❌ Deploy Preview for openapi-ts failed.

Name	Link
🔨 Latest commit	39b374d
🔍 Latest deploy log	https://app.netlify.com/projects/openapi-ts/deploys/68468af36cbe3f00080de692

[changeset-bot]

⚠️ No Changeset found

Latest commit: 39b374d

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

[gzm0]

@duncanbeevers can I hand this over to you? I'm not feeling sufficiently comfortable with the internals to review this.

[duncanbeevers]

@gzm0 Yes I can take this. I think it's a duplicate of a couple other issues, so I'll see about taking some time to gather the various bugs + fixes together to pick the best solution.

[iw-tundo]

Hi, I'm also encountering this issue. Do you know if you have a rough estimate of when this will be merged and released?
@duncanbeevers

[drwpow]

@Newbie012 could you add a patch changeset with a note on the fix? If you add one I’d be happy to merge this as-is. Thanks!

[fluctus]

@Newbie012 @gzm0 @duncanbeevers @sultaniman This is a duplicate of this PR which was not yet merged; you can read the discussion there but the general idea I had is that we should avoid generating root types for enums when these flags are used together, instead of generating an exported type with Schema prefix just for enums, as it would be confusing. WDYT?