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.
Typescript / Types
See original GitHub issueI’d like to know what your plans for typescript is? I’ve seen a twitter post somewhere that you were looking for a conversion tool for JSDoc to TS.
I’ve started creating some types for logux in my app. But it would make more sense if those types ended up in your repository directly so others can benefit, too.
Do you plan to migrate to TS?
Or do you plan to just add .d.ts-files?
I could help with both types and typescript conversion. The important thing is that the types will be kept in sync with the JS if only .d.ts-files will be added.
Issue Analytics
- State:
- Created 4 years ago
- Comments:6 (4 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
Logux got types. I am planning to release it today.
We need a way to use Logux directly from GitHub like
"@logux/core": "logux/core"(without need to call sometime after install). It is useful to test fixes on production.What if we will use approach from my Storeon? We could have separated
.d.tsfile and run TS on CI to check that current code (and tests) with this types to check that types are accurate.The question is how to use TS types in Documentation.js.