Closed rrthomas closed 9 years ago
The reason for this behavior is twofold:
As far as the commit message goes: You can consider almost everything in ufoJS as beeing rooted in http://code.robofab.com/browser/branches/ufo3k/ so if you don't like a specific behavior of ufoJS its probably in robofab, too. The biggest changes I introduced where:
I suggest, as it is not possible to use UFOReader with ufoJS at the moment (because it doesn't exist) that metapolator checks these cases. It's an unfortunate situation of course.
In most cases, this behaviour seems fine (in other words, it's an internal "validation hack"). However, in my particular case it seems unfortunate, as the entire font does not exist. Surely this can result in failure?
This arose from Metapolator issue #134: https://github.com/metapolator/metapolator/issues/134
The problem in this case is that
GlyphSet.js
contains the codeCommit 38cbb962, which seems to be the source of this treating IONoEntryError as "empty" has the unenlightening commit message "started adding async apis for some methods".
So, I guess there's a reason for this behavior, but unfortunately it means that clients aren't told if they've passed a non-existent directory, so they'd have to do their own checks, which isn't terribly logical. Can we fix this?