-
Notifications
You must be signed in to change notification settings - Fork 479
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
Font validate is incomplete #607
Comments
Good catch, would you lake to contribute a PR for this fix, along with some tests to catch this behaviour? |
@Connum are all the assertions a true test for a valid font? For example running the validate function on the Roboto-Black font in the test folder returns these warnings. I would guess that most are just warnings and shouldn't invalidate the font.
Running
|
Good question. I think a font should always at least have all its meta data provided in English, but of course it also works without it. Maybe we need to be able to provide the severieties that we want to get back from that function? But that would require that we categorize errors/warnings by severity in the first place. I would like to get the rest of @opentypejs/owners on board for this. |
I'm currently working on restructuring the error handling. See also #337 and #643. You can check out the work-in-progress branch here, where https://github.com/Connum/opentype.js/tree/WIP/validation-error-handling |
Expected Behavior
Font.validate
should return a boolean or the list of warnings that have been generated.Current Behavior
Font.validate
doesn't do anything.Possible Solution
After asserting return the warnings array.
Context
I'm referencing this method.
The text was updated successfully, but these errors were encountered: