Introduce font related platform implementations for unit tests #7344
Conversation
This file contains 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
Gillibald
force-pushed
the
feature/fullFontTestBackend
branch
from
08b72d2 to
7c3a799
Compare
Gillibald
changed the title
Gillibald
force-pushed
the
feature/fullFontTestBackend
branch
from
d4e5c80 to
ac99c95
Compare
Gillibald
force-pushed
the
feature/fullFontTestBackend
branch
from
ac99c95 to
1855914
Compare
maxkatz6
approved these changes
Jan 22, 2022
danwalmsley
pushed a commit
that referenced
this pull request
Jan 24, 2022
Introduce font related platform implementations for unit tests
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
This PR introduces platform implementations for IFontManagerImpl etc. that solely rely on HarfBuzzSharp that out usable in an environment that doesn't require a rendering backend and still produces the same measures as out render backends in terms of measures etc.
These changes are only unit test-specific.
What does the pull request do?
What is the current behavior?
What is the updated/expected behavior with this PR?
How was the solution implemented (if it's not obvious)?
Checklist
Breaking changes
Obsoletions / Deprecations
Fixed issues