Yoelvis Mulen

Christian, Husband, Father
Engineering Manager at @hello_const
YouTube: /yoelvismulen

[Yoelvis Mulen @ymulenll]

@kettanaito Do you have an example using Symbol.dispose in tests, I haven’t seen that pattern there. It may be a good afterEach alternative.

[Yoelvis Mulen @ymulenll]

La consola de AWS es ideal para aprender sobre la nube, pero para proyectos serios, debes llevar los conceptos a código.

La infraestructura como código (IaC) mejora la eficiencia y escalabilidad.

Descubre cómo en mi este sobre CloudFormation.
@awscloud
https://t.co/McrWHFmMSm

[Yoelvis Mulen @ymulenll]

@kentcdodds I prefer `const` for primitive values because, other than not allowing to reassign them, typescript types will use the literal value instead of the data type. Will `let` will have to do a lot of `as const` to get similar results.

[Yoelvis Mulen @ymulenll]

I never thought I would have dinner near the Redux master @acemarke

Things that happen during @ReactMiamiConf 🏖️

[Robert Balicki (👀 @IsographLabs) @StatisticsFTW]

The best part of ⁦@ReactMiamiConf⁩ isn’t the presentations 😎 @cbnsndwch⁩ ⁦@Vjeux⁩ ⁦@HipsterSmoothie⁩ ⁦@devagrawal09⁩ ⁦@notrlmert⁩ ⁦@acemarke⁩ ⁦@ymulenll⁩ ⁦@jbarnaby⁩ ⁦@vcarl_⁩ ⁦@RyanBradyND05⁩ ⁦@ymulenll⁩

[Yoelvis Mulen @ymulenll]

It was great to hang out with part of the @codeiumdev team, I will check out their extension asap

@kevinhou22

[Gonzalo Darrigrand @DarrigrandG]

109. Entender ¡cambia la vida! La didáctica al servicio público.

Gracias @ymulenll

[Yoelvis Mulen @ymulenll]

It’s time to learn Vim 😉, glad to meet you @ThePrimeagen

@ReactMiamiConf

[Yoelvis Mulen @ymulenll]

Glad to meet the legend @kentcdodds

@ReactMiamiConf

[Yoelvis Mulen @ymulenll]

@phry @TkDodo @acemarke Absolutely, but in case we don't want to drill local state props down, zustand + context is a valid alternative to local state + context. Of course it's for some escenarios, in general prop drilling is ok.

[Yoelvis Mulen @ymulenll]

@acemarke @TkDodo also, that way I could even mount the same Dashboard twice at the same time and it will work, it's not the case with a global store. (I like and use RTK, I am just mentioning one of the challenges I find)

[Yoelvis Mulen @ymulenll]

@acemarke @TkDodo I just want to avoid prop drilling within a "component instance", like the dashboard example that Dominik mentioned in his blog post, it's not feasible with a global store. We have local state + context or a solution like that using zustand instances + cx:
https://t.co/N7zKCfBqkC

[Yoelvis Mulen @ymulenll]

@acemarke I think it's the problem @TkDodo is trying to solve, it's not about getting a global store instance, but different instances for different component subtrees.

[Yoelvis Mulen @ymulenll]

@acemarke I would like to use rtk within a component subtree, not always as a global state, it could simplify the logic in escenarios when I want a fresh state to share within a subtree. That will be initiated with default values when mounted and removed when unmounted like local state.

[Yoelvis Mulen @ymulenll]

@TkDodo yes but it's global/shared for all the components, it would be nice if we could make it a separate instance for different component trees like what you shared about zustand + context

[Yoelvis Mulen @ymulenll]

@TkDodo I am not sure if it would be feasible to have something like that with redux toolkit, since rtk is recommended for one global store.

[Yoelvis Mulen @ymulenll]

@TkDodo I totally agree, something I don't like about global state is that it's not tied to a component "lifecycle" like the local state, but sharing a zustand instance within a context makes a lot of sense. Thanks for sharing.

[Yoelvis Mulen @ymulenll]

Hello friends 👋, who is coming to @ReactMiamiConf, I would like to meet you if you can make it to the event.

[Yoelvis Mulen @ymulenll]

@ReactMiamiConf Thank you, I bought my ticket, looking forward to meet the react community at the event 🙌