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

chore(gatsby,gatsby-link): Export Link as named export #36888

Merged
merged 3 commits into from
Oct 27, 2022

Conversation

tyhopp
Copy link
Contributor

@tyhopp tyhopp commented Oct 26, 2022

Description

For v5 we want to adjust the change in #36312 to make Link a named export from gatsby-link. Full context is in the description of that PR.

Documentation

Shouldn't need a mention in the migration doc because the public API for Link is already a named export from gatsby

Related Issues

[sc-54000]

@gatsbot gatsbot bot added the status: triage needed Issue or pull request that need to be triaged and assigned to a reviewer label Oct 26, 2022
@tyhopp tyhopp removed the status: triage needed Issue or pull request that need to be triaged and assigned to a reviewer label Oct 26, 2022
@tyhopp tyhopp marked this pull request as ready for review October 26, 2022 01:58
@tyhopp tyhopp added this to the Gatsby 5 milestone Oct 26, 2022
@LekoArts LekoArts added the topic: frontend Relates to frontend issues (e.g. reach/router, gatsby-link, page-loading, asset-loading, navigation) label Oct 26, 2022
@LekoArts LekoArts merged commit 5a88dbb into master Oct 27, 2022
@LekoArts LekoArts deleted the chore/gatsby-link-named-export branch October 27, 2022 07:39
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
topic: frontend Relates to frontend issues (e.g. reach/router, gatsby-link, page-loading, asset-loading, navigation)
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants