Best Practice using async await for setState in React Native

Asked Dec 12 '18 at 03:48

Active Dec 12 '18 at 04:00

Viewed 477 times

I'm new in React Native. But i'm aware if this.setState method is run in asynchronous mode.

I have a snippet code like this :

async doSave() {
        await this.props.takeCustomerServiceTicket(this.state.name, this.state.address, this.state.password);
        await this.setState({
            name: '',
            address: '',
            password: ''
        });
    };

What i want to ask are :

Is setState can be await like that? the code not show error, but it really effective to make it await ?
Is my code really synchronous after i use async await like that?
I'm afraid about by reference, are name, address, password that passed via takeCustomerServiceTicket still exist until the function finish ? or it loss because my setState ?

asked Dec 12 '18 at 03:48

Crocodile

`async` and `await` is only syntax sugar, it doesn't magically make asynchronous operations synchronous (which is usually impossible) – CertainPerformance Dec 12 '18 at 04:01
@CertainPerformance : but is it secure do like my code ? – Crocodile Dec 12 '18 at 04:12
There are no security risks in the code you posted, but `await this.setState` still just doesn't make any sense – CertainPerformance Dec 12 '18 at 04:13
Oh ic. is it possible setState running first before takeCustomerServiceTicket ? If yes, i afraid the value loss before using by takeCustomerServiceTicket – Crocodile Dec 12 '18 at 04:15
Shouldn't be an issue, the primitive is effectively copied when the function is called (make sure `takeCustomerServiceTicket` returns a `Promise`) – CertainPerformance Dec 12 '18 at 04:17
name is a String. the text/string not a primitive data type right? – Crocodile Dec 12 '18 at 04:19
No, strings are primitives – CertainPerformance Dec 12 '18 at 04:20

Best Practice using async await for setState in React Native

0 Answers0