-
Notifications
You must be signed in to change notification settings - Fork 51
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
glyph_data has contradictory types #1019
Comments
ouch, my bad. |
@simoncozens let me know if you are working on a fix already, so we don't duplicate work |
Not planning to work on in for the forseeable. |
ok i'll fix that thanks |
schriftgestalt
pushed a commit
that referenced
this issue
Oct 23, 2024
schriftgestalt
pushed a commit
that referenced
this issue
Oct 23, 2024
…t (but only once) Fixes #1019
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
glyphsLib.builder.to_ufos
takes aglyph_data
parameter which is (a) passed topreflight_glyphs
, and (b) passed toUFOBuilder
.In
preflight_glyphs
,glyph_data
is interpreted as:glyphsLib/Lib/glyphsLib/builder/__init__.py
Lines 170 to 171 in 8698f2c
So it's a
GlyphData
object. However, inUFOBuilder
, it is described asglyphsLib/Lib/glyphsLib/builder/builders.py
Line 88 in 8698f2c
What does that mean?
glyphsLib/Lib/glyphsLib/builder/builders.py
Lines 187 to 194 in 8698f2c
Oh, it's a list of paths.
It's historically been a list of paths, but now if you pass a list of paths,
preflight_glyphs
crashes because it's expecting aGlyphData
object:The text was updated successfully, but these errors were encountered: