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.

Sign up for GitHub

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

Jump to bottom

Handle footnote names that have been parsed into multiple nodes #311

Merged
merged 5 commits into from
Jun 7, 2023
Merged

Handle footnote names that have been parsed into multiple nodes #311

merged 5 commits into from
Jun 7, 2023

Commits on Jun 6, 2023

  1. Handle footnote names that have been parsed 

    into multiple nodes. For example `[^_foo]`
gives `^`, `_`, and `foo`.
    @digitalmoksha
    digitalmoksha committed Jun 6, 2023
    Configuration menu
    Copy the full SHA
    58f9ee2 View commit details
    Browse the repository at this point in the history

  2. Refactor to use enum Case in normalize_label

    @digitalmoksha
    digitalmoksha committed Jun 6, 2023
    Configuration menu
    Copy the full SHA
    a027531 View commit details
    Browse the repository at this point in the history

  3. fuzz: gfm_footnotes

    @kivikakk @digitalmoksha
    kivikakk authored and digitalmoksha committed Jun 6, 2023
    Configuration menu
    Copy the full SHA
    02594f1 View commit details
    Browse the repository at this point in the history

  4. inlines: don't crash on empty content here

    @kivikakk @digitalmoksha
    kivikakk authored and digitalmoksha committed Jun 6, 2023
    Configuration menu
    Copy the full SHA
    fd13510 View commit details
    Browse the repository at this point in the history

  5. Clear delimiter stack after processing footnote name

    @digitalmoksha
    digitalmoksha committed Jun 6, 2023
    Configuration menu
    Copy the full SHA
    e80ed0e View commit details
    Browse the repository at this point in the history