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.

Use `any` instead of `unknown`

See original GitHub issue

I’m working on https://github.com/sindresorhus/caprine/issues/848 and I’ve hit a wall when I wanted to receive data from answerRendered function. The problem is passed data is defined in answerRenderer with unknown type which can’t later on be assigned to other values with any other type than unknown.

My best idea is to use type any instead of unknown. Other option is to use unknown type on every ipc handling in Caprine which doesn’t sound very nice to me.

@BendingBender I’d love your thoughts on this too since you wrote up TypeScript definitions.

Issue Analytics

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

Top GitHub Comments

1reaction

dusansimiccommented, Oct 8, 2019

Well, when I call callMain I can specify data type for the data parameter that will be passed to the callback but in answerRenderer definition data parameter in callback is always defined as unknown (generic type cannot change it) hence the error is thrown.

A two generic types would be useful since then, developer can specify both the type of data that is received and the type of data that is sent back.

0reactions

vladimirycommented, Nov 19, 2019

@dusansimic you could try https://github.com/vladimiry/electron-rpc-api if you need methods signatures, including the payload type, to be fully typed/predefined.