Typescript errors after upgrade
See original GitHub issueAfter upgrading to the latest version of Sade, I’m getting the following type error on my action
s:
Argument of type '(service: string, opts: Options) => Promise<void>' is not assignable to parameter of type
'Handler<[service: string]>'.\n Types of parameters 'opts' and 'args_1' are incompatible.\n
Type 'Argv<Default>' has no properties in common with type 'Options'.
Issue Analytics
- State:
- Created 2 years ago
- Reactions:2
- Comments:5 (2 by maintainers)
Top Results From Across the Web
Build errors after updating to Angular 9 and Typescript 3.8.3
Roll back to angular 9, and then start debugging. I've upgraded 2 projects from 5 to 9. When I had errors, that was...
Read more >Typescript problem after vs update - Visual Studio Feedback
My project don't compile in last version of visual studio, i get this compile error "Your project is built using TypeScript 2.3, but...
Read more >Documentation - TypeScript 3.9
Pick ts-ignore if: you have a larger project and new errors have appeared in code with no clear owner; you are in the...
Read more >How to Upgrade to TypeScript Without Anybody Noticing
checkJs — Give errors on JS files. noEmit — Don't emit downlevel code; just give errors. target — Target the newest version of...
Read more >TypeScript errors and how to fix them
error TS2391: Function implementation is missing or not immediately following the declaration. Broken Code ❌. 1 2 3 4
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
No worries, thanks for your work on it!
It was meant to be something like
.action<[string]>((value, options) => { ... })
whereoptions
was automatically typed withmri.Argv.Default
, but that didn’t allow you to add more explicit types foroptions
which is/was problematic.Publishing a patch now. Sorry for the trouble!