You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I just opened a package update PR for hydra which bumps oxifmt from 0.2.0 to 0.2.1 (see packages#1513). In the previous version, oxifmt still used the backwards compatible behavior of type("") == "string". This means that any package using oxifmt 0.2.0 and below on the current development version of Typst (bb38a01) will simply fail because the format argument to oxifmt.strfmt never passes the string type check.
It would probably be a good idea to upstream check which other dependencies use an older version of oxifmt and if they have bumped it yet before releasing 0.1.0.
PS: very excited to check out the new version, looks pretty good from what I've seen.
The text was updated successfully, but these errors were encountered:
I just opened a package update PR for hydra which bumps oxifmt from
0.2.0
to0.2.1
(see packages#1513). In the previous version, oxifmt still used the backwards compatible behavior oftype("") == "string"
. This means that any package using oxifmt0.2.0
and below on the current development version of Typst (bb38a01
) will simply fail because the format argument tooxifmt.strfmt
never passes the string type check.It would probably be a good idea to upstream check which other dependencies use an older version of oxifmt and if they have bumped it yet before releasing
0.1.0
.PS: very excited to check out the new version, looks pretty good from what I've seen.
The text was updated successfully, but these errors were encountered: