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

[v3] Access <Link>s underlying node via innerRef #6340

Merged
merged 1 commit into from Sep 18, 2018

Conversation

pascalduez
Copy link

Hi,

this is essentially a port of #5294 to v3.

@pascalduez pascalduez changed the title Access <Link>s underlying node via innerRef [v3] Access <Link>s underlying node via innerRef Sep 18, 2018
@timdorr
Copy link
Member

timdorr commented Sep 18, 2018

LGTM. Thanks!

@timdorr timdorr merged commit 528e28f into remix-run:v3 Sep 18, 2018
@pascalduez
Copy link
Author

pascalduez commented Sep 19, 2018

@timdorr Thanks, would you have an eta for a release? :)

@timdorr
Copy link
Member

timdorr commented Sep 19, 2018

No idea. Nothing is planned for 3.0 currently.

@diondiondion
Copy link

+1 for releasing this as a patch for us poor souls still stuck with version 3. This is quite an essential feature. :)

4u added a commit to 4u/react-router that referenced this pull request Nov 19, 2018
* 'v3' of github.com:ReactTraining/react-router:
  Access <Link>s underlying node via `innerRef` (remix-run#6340)
  3.2.1
  Update a bunch of other deps.
  Make switching from master to v3 even easier.
@yowakita
Copy link

yowakita commented Dec 4, 2018

@timdorr I'm a little confused on what this means, does that mean that something is missing before this feature is able to go out? I see that the code change was merged to master and the package.json reflects version as 3.2.1, and there was a npm release for 3.2.1 9 months ago - what would it take for v3 to be bumped to 3.2.2 and include this change?
I'd love to help out in some way if thats necessary.

@lock lock bot locked as resolved and limited conversation to collaborators Feb 2, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

4 participants