Feat: Add support for pattern properties

[hontas]

Changes

Add support for patternProperties in addition to additionalProperties (#754).
Building on the work of @gzm0 in 1901 by adding tests

Ran the command pnpm run update:examples which created 129 new files and updated 69, none of which seemed related to this change. Let me know if you wan't me to do it anyways.

How to Review

Refer to comments in original PR 1901
Validate tests are satisfactory

Checklist

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

[netlify]

✅ Deploy Preview for openapi-ts canceled.

Name	Link
🔨 Latest commit	d6d0f0e
🔍 Latest deploy log	https://app.netlify.com/projects/openapi-ts/deploys/68a440fe754dd200082462cf

[changeset-bot]

🦋 Changeset detected

Latest commit: d6d0f0e

The changes in this PR will be included in the next version bump.

This PR includes changesets to release 2 packages

Name	Type
openapi-typescript	Minor
swr-openapi	Major

Not sure what this means? Click here to learn what changesets are.

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

[gzm0]

@kerwanp LMK if you'd like to hand-off review to me here.
@hontas TY so much for taking this over!

[drwpow]

@gzm0 yes please feel free to review! The round-robin assignment was only meant to divide the PR reviews among us evenly, but always feel free to jump in and stamp a PR if you have context/time

[bRRRITSCOLDtkww]

Any more movement on this?

[hontas]

@gzm0 thanks for the feedback!
I have updated to what I think you meant. Please have a look 🙏

[gzm0]

Nice! Sorry for the delay on this one.

The behavior looks good. There is just a control flow concern. Then I think we can ship this.

[gzm0]

This should not happen, but if it does, the behavior is horrible: it will completely ignore coreObjectType and just return undefined.

My recommendation is to remove the initial if (schemaObject.additionalProperties || options.ctx.additionalProperties || schemaObject.patternProperties) { and basically always calculate addlTypes (maybe call it stringIndexTypes or something).

Then you can, at the end of the function:

if (addlTypes.length == 0) {
   return coreObjectType.length ? ts.factory.createTypeLiteralNode(coreObjectType) : undefined;
}

return tsIntersection( // etc....)

Just in case I got it completely wrong what is happening here and this code is actually reachable (and necessary), please add a test case for it (or point out to ignorant me, which existing test case covers this :P).