-
Notifications
You must be signed in to change notification settings - Fork 156
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
kwalify for YAML validation #570
Comments
I'm aware of the task, give me some time to find a developer... |
thanks for the ticket, your account was topped for 15 mins, payment 000-a294daaf |
@aistomin it's in your hands now, please proceed |
@aistomin you're holding this ticket for 13 days already. If it's not finished (and closed) in the next 24 hours, it will be re-assigned to someone else, see No Obligations principle |
@aistomin you've been working with this task for too long. I'm sorry, but I'll assign someone else. Please stop working with it. See our no obligations principle |
@krzyk the task is yours |
@krzyk just a reminder that you're working with this task for 11 days already |
@alex-palevsky give me more time please |
@krzyk OK, take your time |
@phlipper thanks for the hint, I have nothing against safe_yaml |
@phlipper safe_yaml looks like only a library for ruby to parse yaml, I don't see any command line utility for it, and I don't see any schema definition that could be used (kwalify has both) |
@yegor256 you mean to validate if .rultor.yml is valid or is it conforming to a given schema (a subset of YAML)? I think that the first part is already done by SnakeYAML, but I want to make sure. |
@krzyk I want to make sure that |
PR #691 |
the code made here contains a puzzle |
@yegor256 PR has been merged, please close this issue, thanks |
thanks! |
let's use kwalify for
.rultor.yml
validation before processing: http://www.kuwata-lab.com/kwalify/ruby/users-guide.html570-b7bcc1c2
/GithubProfile.java:247-250: Implement validation using Kwalify library... #699 (by )The text was updated successfully, but these errors were encountered: