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

Move tests that include ion data into locations under an ion subpath #129

Merged
merged 1 commit into from
Dec 4, 2024

Conversation

jpschorr
Copy link
Contributor

This PR seeks to make make it clear where Ion data is used in the partiql-tests.

Many places quoted Ion was used where it was unneccesary, and is thus replaced.
For example:

  • [`true`] is replaced with [TRUE]
  • {a: 1} is replaced with {'a': 1}

In places that Ion data is appropriate and used to test integration with Ion, the test cases are moved into new files under an ion sub-directory.


By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

@@ -0,0 +1,9 @@

// TODO [joshsp] : In a lazy-document context, this is a data error, not a syntax error
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

So perhaps this test along w/ the test in partiql-tests-data/fail/syntax/ion/primitives/time-constructor.ion should still successfully parse?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

true

@@ -191,18 +191,6 @@ cardinality::[
output:1
}
},
{
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Should this test also be replicated using non-Ion syntax

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

cardinality({'a': 'missing'}) ?

@jpschorr jpschorr merged commit 85a01fb into main Dec 4, 2024
4 checks passed
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