Skip to content

Conversation

@AlbinaBlazhko17
Copy link
Contributor

@AlbinaBlazhko17 AlbinaBlazhko17 commented Nov 28, 2025

What/Why/How?

  • Added using new setter method to set on demand default unevaluated properties.
  • Refactored no-invalid-media-type-examples, no-invalid-parameter-examples, no-invalid-schema-examples rules.
  • Set to validateExamples function default property of defaultUnevaluatedProperties to true due to OpenApi spec. OpenApi spec by default sets additionalProperties for objects to true.

Reference

Resolves #2410

Testing

Ran tests and added new, which cover specific case.

Screenshots (optional)

Check yourself

  • Code changed? - Tested with Redoc/Realm/Reunite (internal)
  • All new/updated code is covered by tests
  • New package installed? - Tested in different environments (browser/node)
  • Documentation update considered

Security

  • The security impact of the change has been considered
  • Code follows company security practices and guidelines

@AlbinaBlazhko17 AlbinaBlazhko17 self-assigned this Nov 28, 2025
@changeset-bot
Copy link

changeset-bot bot commented Nov 28, 2025

⚠️ No Changeset found

Latest commit: 15c2433

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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

no-invalid-media-type-examples not triggering warning for unevaluated properties

2 participants