Possible bug due to unnecessary rerenders about easy-peasy

[NilsBaumgartner1994]

one solution is to memorize the component with the optionValue. My initial though was that i could get the same instance of the methods back?

// memoize this component
function MyButtonRowWithOptionKey ({optionKey}: {optionKey: string}) {
	const {optionValue, specificFlipOption} = useFlipOptionsWithKey(optionKey);

	return useMemo(() => {
		console.log(`Rendering MyButtonRowWithOptionKey ${optionKey}`)

		return (
			<View>
				<Text>{optionKey+": "+optionValue}</Text>
				<TouchableOpacity style={{
					backgroundColor: 'orange',
					padding: 10,
					margin: 10,
				}} onPress={specificFlipOption}>
					<Text>Flip {optionKey}</Text>
				</TouchableOpacity>
			</View>
		)
	}, [optionValue])
}

[jmyrland]

Hey @NilsBaumgartner1994 !

I don't get it, why in this simple example the components MyButtonRowWithOptionKey are rerendering both, despite i only change a value in one?

Both components are re-rendered in both cases because both are dependent on the options object in the store.

When updateOptions is called, the options reference is updated (to the new object), which in turn triggers a rerender for all components depending on options from the store.

If you want to "fix" this in the store, you'd have to split the options into separate values in the store & update these individually.

Hope that clarifies things.

one solution is to memorize the component with the optionValue

Given that the options values are primitives, your example should prevent view-rerenders for unchanged options values.

[NilsBaumgartner1994]

I found where the problem was:

The rerender was caused due to the option reference being updated. So as you said it triggers a rerender for all components depending on that.

If you want to "fix" this in the store, you'd have to split the options into separate values in the store & update these individually.

My solution would be this. Seems a bit easier in my optionion?

// BAD
const options = useStoreState((state) => state.options);
const optionValue = options?.[optionKey];

// Correct
const optionValue = useStoreState((state) => state.options?.[optionKey]);

[NilsBaumgartner1994]

@jmyrland is my solution overlooking something?

[jmyrland]

I found where the problem was:

The rerender was caused due to the option reference being updated. So as you said it triggers a rerender for all components depending on that.

If you want to "fix" this in the store, you'd have to split the options into separate values in the store & update these individually.

My solution would be this. Seems a bit easier in my optionion?

// BAD
const options = useStoreState((state) => state.options);
const optionValue = options?.[optionKey];

// Correct
const optionValue = useStoreState((state) => state.options?.[optionKey]);

I think that should work. It should only rerender when the options[optionKey]-state changes 👍

My only concern is; what happens if options?.[optionKey] resolves to undefined. If you have tested this, and it works - you should be fine 👌