fix: forward refs to <PrismicLink>
components
#131
Merged
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.
Types of changes
Description
This PR adds support for forwarding refs to
<PrismicLink>
components. Before this PR, refs were ignored, meaning there was no way to target the rendered element.In the following example,
ref
will contain a reference to the rendered<a>
element.If a custom component is provided, the ref will be passed to the component. The custom component must handle the ref forwarding itself.
This works for both internal and external components. If you are using TypeScript, note that this means the ref must be typed for both the rendered internal and external components.
Fixes #128
Checklist:
🐡