Skip to content
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

[api-minor] Initialize the unicode-category *lazily* on the Glyph-instance #15665

Merged
merged 1 commit into from
Nov 5, 2022

Commits on Nov 5, 2022

  1. [api-minor] Initialize the unicode-category *lazily* on the Glyph-i…

    …nstance
    
    The purpose of this patch is twofold:
     - Initialize the unicode-category data *lazily* during text-extraction, since this is completely unused during general parsing/rendering.
     - Stop exposing this data in the API, since it's unused on the main-thread and it seems like it was *accidentally* included.
    
    Obviously these changes are API-observable, but hopefully no user is depending on this. Furthermore, it's trivial for a user to re-create this unicode-category data manually with a regular expression (from the exposed `unicode` property).
    Snuffleupagus committed Nov 5, 2022
    Configuration menu
    Copy the full SHA
    c8868a1 View commit details
    Browse the repository at this point in the history