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

fix(gatsby): Wrong route resolved by findPageByPath function #34070

Merged
merged 6 commits into from
Jan 4, 2022
Merged

fix(gatsby): Wrong route resolved by findPageByPath function #34070

merged 6 commits into from
Jan 4, 2022

Commits on Dec 3, 2021

  1. use best matching route

    @tlgimenes
    tlgimenes committed Dec 3, 2021
    Configuration menu
    Copy the full SHA
    d4c4b17 View commit details
    Browse the repository at this point in the history

  2. add more comments

    @tlgimenes
    tlgimenes committed Dec 3, 2021
    Configuration menu
    Copy the full SHA
    57bb52d View commit details
    Browse the repository at this point in the history

  3. add tests

    @tlgimenes
    tlgimenes committed Dec 3, 2021
    Configuration menu
    Copy the full SHA
    746662a View commit details
    Browse the repository at this point in the history

Commits on Jan 3, 2022

  1. Merge remote-tracking branch 'origin/master' into tlgimenes-master

    @pieh
    pieh committed Jan 3, 2022
    Configuration menu
    Copy the full SHA
    c332a97 View commit details
    Browse the repository at this point in the history

Commits on Jan 4, 2022

  1. add matchPath specifity tests to findPageByPath

    @pieh
    pieh committed Jan 4, 2022
    Configuration menu
    Copy the full SHA
    2c04d67 View commit details
    Browse the repository at this point in the history

  2. add note about possible optimalization for matchPath handling

    @pieh
    pieh committed Jan 4, 2022
    Configuration menu
    Copy the full SHA
    300ef5e View commit details
    Browse the repository at this point in the history