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

test: test validating a schema name that could "trick" JavaScript #250

Merged
merged 4 commits into from
Sep 4, 2024

Conversation

EvanHahn
Copy link
Contributor

@EvanHahn EvanHahn commented Sep 4, 2024

I was worried that bad schema names like hasOwnProperty or constructor could cause trouble. They don't (as far as I can tell) but I still think it's worth adding a fixture for it.

Previously, we intended to test the validation of bad docs but weren't
doing so correctly. This fixes that.
@EvanHahn EvanHahn requested a review from gmaclennan September 4, 2024 14:43
I was worried that bad schema names like `hasOwnProperty` or
`constructor` could cause trouble. They don't (as far as I can tell) but
I still think it's worth adding a fixture for it.
@EvanHahn EvanHahn force-pushed the validate-hasownproperty branch from 8e10bc7 to 51bca96 Compare September 4, 2024 14:44
Base automatically changed from change-validate-tests to main September 4, 2024 15:21
@EvanHahn EvanHahn merged commit 9e78a72 into main Sep 4, 2024
6 checks passed
@EvanHahn EvanHahn deleted the validate-hasownproperty branch September 4, 2024 15:30
gmaclennan added a commit that referenced this pull request Sep 9, 2024
* main:
  test: test validating a schema name that could "trick" JavaScript (#250)
  test: properly test more `validate` errors (#249)
  fix: observation metadata types (#248)
  chore: remove `any`s from decode helper function (#247)
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.

2 participants