Bug fix for Typst Version 0.13. #12
Open
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Bug Fixes for Typst Template
typstversion: >= 0.13.1Issues Fixed
1. Deprecated Type Comparisons
Problem: Comparing types with strings is deprecated and will return
falsein future releases.Locations:
type(date) == "datetime"type(date) == "dictionary"type(logo) == "content"type(abstract) == "content"Solution: Changed to compare with literal types instead:
2. Invalid Selector Usage with
locate()Problem: Only element functions can be used as selectors. The
locate()function is deprecated in certain contexts.Locations:
Solution: Replaced
locate()withcontextexpressions:3. Context Required for Counter Operations
Problem: Page counter operations require context to be known.
Location: Line 112-115: Footer page numbering
Solution: Wrapped counter operations in
contextblock and converted final count to string:4. Deprecated
image.decode()Problem:
image.decode()is deprecated in favor of passing bytes directly toimage().Location: Line 213: ORCID logo rendering
Solution:
bytes()functionimage()instead of usingimage.decode()5. Deprecated
par set blockChange
show par: set block(...)toset par(...)as typst (as of 0.13) suggests.