Resolved missing font family on dynamic IconBlock components#23
Merged
ergoxiv merged 1 commit intoAether-Tools:Anamnesisfrom Feb 9, 2026
Merged
Conversation
ergoxiv
changed the title
ergoxiv
force-pushed
the
hotfix/fontawesome-invalid-fontfamily
branch
from
6ee4eb1 to
21fa9d8
Compare
ergoxiv
changed the title
StoiaCode
approved these changes
Feb 8, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Aims to address imchillin/Anamnesis#1571.
When treating icon property updates, it seems that FontAwesome.Sharp checks the font family, which when not explicitly set, might raise errors as the ones reported in the GitHub issue.