Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Export Types

See original GitHub issue

Would it be possible to export the types used in this project. i want to extend some functionallity and need to copy&paste many of them to my code, so i can access them.

i.e: CaseReducerActions, RestrictCaseReducerDefinitionsToMatchReducerAndPrepare, …

Issue Analytics

State:
Created 4 years ago
Comments:11 (6 by maintainers)

Top GitHub Comments

2reactions

phryneascommented, Dec 10, 2019

Hi @wuifdesign, some of these types are deliberately not exported, as they are really just useful internally and we might replace them with simpler types as we find better solutions. As soon as we export an internal type, essentially we have to support it forever and can never change it to not break things for people. Especially RestrictCaseReducerDefinitionsToMatchReducerAndPrepare is a type that I am expecting to remove soon using the technique displayed in this playground.

Exporting CaseReducerActions would also require us to export SliceCaseReducerDefinitions, which relies on PayloadActions and some of these might also become obsolete using the same technique.

Could you please explain with a few code snippets what you are trying to do? Maybe I can help you around your problems with only our exported types - and maybe that’ll even lead to something we can add to our TypeScript documentation afterwards 😃

PS: using those types should not be necessary for you and should even be avoided, as overspecifying your types instead of using inteference will erase useful type information and make your types overall worse in the end.

1reaction

wuifdesigncommented, Jan 2, 2020

@phryneas thx, i already saw it, and i will try it after holidays