-
Notifications
You must be signed in to change notification settings - Fork 29
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
feat(ConfigForm): Add support for oneOf fields #1551
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I do not understand what to look at and verify exactly. What is modified functionally?
I tried in VS Code and I can still create routes.
assertFalse(properties.has("langChain4jCharacterTokenizer")); | ||
assertFalse(properties.has("langChain4jLineTokenizer")); | ||
assertFalse(properties.has("langChain4jParagraphTokenizer")); | ||
assertFalse(properties.has("langChain4jSentenceTokenizer")); | ||
assertFalse(properties.has("langChain4jWordTokenizer")); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
to help understand error failure, it is convenien tto provide an error message on the reason
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Added
} | ||
|
||
@Test | ||
public void testRemoveEmptyProperties() throws Exception { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
in JUnit 5, it is recommended to not use the the public modifier and keep default package
https://junit.org/junit5/docs/current/user-guide/#writing-tests-classes-and-methods
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Ok, I updated all tests to follow that convention
Currently, we have partial support for the `oneOf` schemas. This commit cleans up the generated schemas, by removing the `not` definition from `oneOf` and also removing the empty properties like: ''' { property: { } } ''' fix: KaotoIO#1550 fix: KaotoIO#948
80a26ff
to
baf4bbd
Compare
Quality Gate passedIssues Measures |
Codecov ReportAttention: Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## main #1551 +/- ##
=======================================
Coverage ? 80.02%
Complexity ? 272
=======================================
Files ? 276
Lines ? 7825
Branches ? 1496
=======================================
Hits ? 6262
Misses ? 1502
Partials ? 61 ☔ View full report in Codecov by Sentry. |
Adding support for In the past,
I wouldn't expect less 😅 |
Context
Currently, we have partial support for the
oneOf
schemas.This commit cleans up the generated schemas, by removing the
not
definition fromoneOf
and also removing the empty properties like:Test the changes live: https://lordrip.github.io/kaoto/
fix: #1550
fix: #948