-
Notifications
You must be signed in to change notification settings - Fork 13
[ENH]: Adopt Pydantic for schema validation #364
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
base: main
Are you sure you want to change the base?
Conversation
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## main #364 +/- ##
===========================================
+ Coverage 91.64% 100.00% +8.35%
===========================================
Files 146 1 -145
Lines 5862 1 -5861
Branches 934 0 -934
===========================================
- Hits 5372 1 -5371
+ Misses 318 0 -318
+ Partials 172 0 -172
Flags with carried forward coverage won't be shown. Click here to find out more.
🚀 New features to boost your workflow:
|
08a5ef0 to
db6b178
Compare
|
|
CI passes on juseless. |
|
@fraimondo I have run quite a few of the YAMLs I have, would appreciate if you could run a couple of your most-used YAMLs with this branch. The YAMLs might require minimal changes which should be evident from the error raised. |
Are you requiring a new dataset or marker?
Which feature do you want to include?
We want to be able to validate the yaml so we avoid issues like #296
How do you imagine this integrated in junifer?
Use pydantic and validate the yaml.
Do you have a sample code that implements this outside of junifer?
No response
Anything else to say?
No response