Add LinkContainer.js

[jquense]

I’m not quite sure this the right setup, but I think Gatsby really needs to prove a way to create links without needing to always render a DOM <anchor>. BEFORE anyone jumps in to say that that is not accessible, that’s silly. There isn’t any way without this to render navigation links from UI components, components that do render an anchor but also have other logic on top of it. Like react-bootstraps NavLink component. A presentational wrapper around an <a>

[jquense]

also what value is @react/router Link doing here? GatsbyLink seems to be overriding all the click logic?

[pieh]

I think @reach/router Link currently just make use of getProps to add conditional props to underlying a element depending if page is active ( https://reach.tech/router/api/Link )

[pieh]

propTypes here have required location which is not not there at exported component level - it get's added by <Location> in code below

[LekoArts]

Hey @jquense 👋 I'm not too sure what your PR is doing, so that's why I'm asking:
Does #9892 solve your problem?

[jquense]

unfortunately no. This is about controlling what component Link renders as an anchor, not getting access to the ref

[DSchau]

@jquense I think we can improve this behavior upstream, rather than introducing this workaround in our own code.

I've opened a PR for reach-router (reach/router#226) to accept an as prop, which will allow you to pass in whatever element you'd like. In theory, as long as your component forwards the ref (and you can easily make a wrapper for this for a bootstrap link, or whatever) then this would allow you to implement this functionality, correct?

Since we forward all props directly to the Link element from @reach/router, I think this will work as is without merging this PR (once/if the one in @reach/router is merged).

I'm not super familiar with react-bootstrap, so if you have an example that would be 👌 .

[DSchau]

@jquense I'm going to close this--we should defer to that upstream behavior PR modification (reach/router#226) that will hopefully get merged soon.

I think that's a little cleaner and it's nice to get the benefit for free rather than making changes here.

As always--thanks for the PR. Sorry for the delay on this one!