-
Notifications
You must be signed in to change notification settings - Fork 586
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
[Subscription API] OAS schema for filter expressions seems not to be correct #1038
Comments
Also references to the SqlFilter schema (see below) are a problem in the
|
@HenriKorver thanks! Would you be interested in submitting a PR ? |
This issue is stale because it has been open for 30 days with no |
/remove-lifecycle stale |
This issue is stale because it has been open for 30 days with no |
/remove-lifecycle stale |
This issue is stale because it has been open for 30 days with no |
/remove-lifecycle stale |
This issue is stale because it has been open for 30 days with no |
Trying the understand the CE filter expressions, I have converted the OAS schema for the Subscription API to JSON Schema (see at the bottom of this message). This allows me to validate CE filter expressions in well-known tooling like Altova XMLSpy.
It appeared that correct CE filter expressions like
are unfortunately not validated by the tool. The reason for this is the
Filter
schema object which matches everything. If this object is used in aoneOf
construction than you always have more than two matches. This problem can easily be solved by removing the reference to theFilter
object in eachoneOf
construction.In the JSON schema which I derived from the OAS (see below), I have only included those parts that are relevant for filter expressions for compactness.
The text was updated successfully, but these errors were encountered: