Component prop to Link and NavLink

Question

Component prop to Link and NavLink

klis87 opened this issue 6 years ago · 7 comments

I need to pass custom component to Link and Navlink to make it work with react-bootstrap components, and I made a PR for this #42 which was rejected because RUDY was supposed to be released, but it is not and won't be any time soon, would you accept this PR if I rebased to current master?

Answer 1 · 2019-01-12T21:48:07.000Z

It’s delayed yes. But in development.

I’ll have to consult with James and my other engineers on accepting a “for now” PR.

It will require documentation and tests. If flow is in there, please make sure flow passes.

Answer 2 · 2019-01-13T11:04:21.000Z

@ScriptedAlchemy I am aware, checking it from time to time, I cannot wait for it, will be so awesome!

But in the meantime things like component and render props would be cool to add here. I will make sure to add necessary tests and that flow is not broken, but one question though, I noticed a PRs related to render prop. Will it be merged soon? I think we should synchronize this, because I will for sure introduce conflicts by adding component, so it would be cool to add it first.

Answer 3 · 2019-01-13T16:25:54.000Z

Tag me in a PR and it will be so.

Docs, flow, and tests please

We’ve had a few merges that’s broke flow and caused everyone headaches :)

Answer 4 · 2019-01-14T16:01:14.000Z

@ScriptedAlchemy I just wanted to start working on it, but yarn run flow throws maaany errors, like:

  5: import type { ComponentType } from 'react'
                   ^^^^^^^^^^^^^ Named import from module `react`. This module has no named export called `ComponentType`.

so what should I do? I could add typings for new component prop, but this won't fix outstanding issues.

Answer 5 · 2019-01-14T16:03:21.000Z

@ScriptedAlchemy linting is also broken, like:

Cannot read property 'type' of undefined
TypeError: Cannot read property 'type' of undefined
    at isForInRef (/home/klis87/projects/redux-first-router-link/node_modules/eslint/lib/rules/no-unused-vars.js:406:24)

Answer 6 · 2019-01-15T03:12:10.000Z

Booo. Okay I’ll have to find time to look into patching this. If you happen to fork or fix anything as well PR me. Otherwise I’ll try to fix it up this week

Answer 7 · 2019-01-15T08:43:52.000Z

Cool, thx! Just wondering how it is possible that travis doesn't complain about linting and flow in recent commits :o