Skip to content

json schema: fix Criterion Object #338

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

Open
wants to merge 1 commit into
base: main
Choose a base branch
from

Conversation

markus-96
Copy link
Contributor

see #336

this is my first PR to this project, so I am happy if you tell me if it meets your expectations :)

If needed, I can also try to take part in the meeting coming in two weeks.

reading #337 (comment) ("Need to digest #336 before discussing"), maybe this helps:

I would consider the following class diagram for modelling a Criterion Object:

grafik

Copy link
Contributor

@jeremyfiel jeremyfiel left a comment

Choose a reason for hiding this comment

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

If the spec remains unchanged, couple things can be updated in this schema version

- simple
- regex
- jsonpath
- xpath
default: simple
- $ref: '#/$defs/criterion-expression-type-object'
type: string
Copy link
Contributor

Choose a reason for hiding this comment

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

unnecessary because the enums are only strings

Suggested change
type: string

type:
description: The type of condition to be applied
default: simple
oneOf:
Copy link
Contributor

Choose a reason for hiding this comment

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

this can be anyOf

@frankkilcommins
Copy link
Collaborator

@markus-96 thanks for the PR. Would you be able to take a look at the feedback from @jeremyfiel? Also, can you target v1.0-dev branch with this PR?

@frankkilcommins
Copy link
Collaborator

@markus-96 appreciate your patience here. I was holding off on approving during to pending infra changes. Those infra changes are not merged, and we've changed the schema directory locations to align with the OpenAPI Specification repos.

Would you be able to update your PR to make the changes against the new schema locations, and also take a look at @jeremyfiel comments above?

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.

3 participants