Skip to content

Fixes an issue where object properties that are not present in the schema are proxied or observed #7186

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.

Sign up for GitHub

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

Jump to bottom
Merged
merged 2 commits into from
Sep 20, 2025
Merged

Fixes an issue where object properties that are not present in the schema are proxied or observed #7186

merged 2 commits into from
Sep 20, 2025

Conversation

janechu
Copy link
Collaborator

@janechu janechu commented Sep 19, 2025 •
edited
Loading

Pull Request

📖 Description

This change ensures that proxied data is matched with the JSON schema.

✅ Checklist

General

  • I have included a change request file using $ npm run change
  • I have added tests for my changes.
  • I have tested my changes.
  • I have updated the project documentation to reflect my changes.
  • I have read the CONTRIBUTING documentation and followed the standards for this project.

@janechu janechu merged commit 3f1fbb3 into main Sep 20, 2025
11 checks passed
@janechu janechu deleted the users/janechu/fix-data-schema-mismatch branch September 20, 2025 21:23
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

@chrisdholt chrisdholt Awaiting requested review from chrisdholt chrisdholt is a code owner

@radium-v radium-v Awaiting requested review from radium-v radium-v is a code owner

Assignees

No one assigned

Labels

None yet

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

1 participant

@janechu