Does useState() a default value when the state key already set ?

The doc is unclear on the topic and my tests show contradictory results.

Let's say I call a component multiple times with

//component A

const foo = useState('foo', ()=>{user: null})
foo.value.user = 'toto';

//component A

const foo = useState('foo', ()=>{user: null})
foo.value.user = 'toto';

//component B

const foo = useState('foo', ()=>{user: null})
foo.value.user = 'bar';

//component B

const foo = useState('foo', ()=>{user: null})
foo.value.user = 'bar';

will the second useState() be reset to

{user: null}

{user: null}

then to

{user: 'bar'}

{user: 'bar'}

or is useState smart enough to know it aleady has a value and to not reinstantiate itself ?

Nuxt•2y ago•

22 replies

Does useState() a default value when the state key already set ?

The doc is unclear on the topic and my tests show contradictory results.

Let's say I call a component multiple times with

//component A

const foo = useState('foo', ()=>{user: null})
foo.value.user = 'toto';

//component A

const foo = useState('foo', ()=>{user: null})
foo.value.user = 'toto';

//component B

const foo = useState('foo', ()=>{user: null})
foo.value.user = 'bar';

//component B

const foo = useState('foo', ()=>{user: null})
foo.value.user = 'bar';

will the second useState() be reset to

{user: null}

{user: null}

then to

{user: 'bar'}

{user: 'bar'}

or is useState smart enough to know it aleady has a value and to not reinstantiate itself ?

Join the Discord to ask follow-up questions and connect with the community

Nuxt Community Chat Server

31,632 Members