Reactotron.log + typescript - cannot invoke an object which is possibly 'undefined'

[doronnac]

reactotron-react-native v4.0.3

import Reactotron from 'reactotron-react-native'
Reactotron.log() // <-- Cannot invoke an object which is possibly 'undefined'

Saw a similar issue which was supposedly resolved. Maybe I'm missing something?

[DavidNeiOs]

I found a temporary solution in this thread #168 (comment)
@doronnac

[leotm]

Since in our ReactotronCore interface log?: (...args: any[]) => void is an optional function, we just need to assert it's not null when calling it:

Reactotron.log!('hey there')

Same goes for any other optional functions you're calling like warn, error, etc.

Use newer optional chaining (TS 3.7+) if preferred.

Bonus: Here's a way to add type safety with linting

[patrick-narciso]

The @leotm solution is correct, it even works for other cases such as when using Reactotron.createEnhancer!()

[AndreCosta101]

The @leotm solution is correct, it even works for other cases such as when using Reactotron.createEnhancer!()

Hey Patrick... you mean in the store configuration? How did you do it ? thanks

[david-bishop-levelstudio]

Hey Patrick... you mean in the store configuration? How did you do it ? thanks

@AndreCosta101 Something like this:

import { createStore } from "redux";
import Reactotron from "../ReactotronConfig";
import rootReducer from "./reducers";

export default createStore(rootReducer, Reactotron.createEnhancer!());

[GermaVinsmoke]

But this solution gives this warning - "Forbidden non-null assertion."
Is it okay to have this warning?

[leotm]

@GermaVinsmoke

Use newer optional chaining if preferred.

Reactotron.log?.('hey there')

Since TypeScript 3.7