Antonio Cestari.

A dev who loves to learn, discuss and teach.

[Antonio Cestari. @ntoniocp]

"When you're your biggest judge you can become your own jaler"

[Antonio Cestari. @ntoniocp]

@kentcdodds YES

[Antonio Cestari. @ntoniocp]

@jamesqquick So what we should be questioning is why do we need so many visual clues for the same thing?, what are users actually used to? How biased are we based on our own preference? Why should a library introduce a default that doesn’t align with the regular user’s OS ui? Optional is 👍🏼

[Antonio Cestari. @ntoniocp]

@jamesqquick Libraries often value having more universal solutions to fulfill the needs of a bigger audience and that’s good.

There are web pages that use hover animations for things that aren’t clickable, so they create the need to distinguish clickable things with solutions like the cursor

[Antonio Cestari. @ntoniocp]

@zan2434 @eddiejiao_obj @drewocarr This looks very cool. Altho, could be nice if A11y was considered from the gecko. With no markup language, and no structured content, what would be the strategy to work with assistive tech?

[Antonio Cestari. @ntoniocp]

@housecor We can stay in the loop evaluating it’s results when it has finished. So if we have that dead time, parallel work starts making sense.

Considering the volume of code we need to review now, working on improving that skill by reviewing several agents outputs also makes sense

[Antonio Cestari. @ntoniocp]

@housecor If tasks are well scoped, and we have enough examples and decisions documented in the codebase for agents to reference, and we always plan first then build. Agents get ~90% of it right first, then we iterate. I don’t find useful to see its “thinking” in real-time

[Antonio Cestari. @ntoniocp]

@jfdelarosa Señales de humo 👍🏼

[Antonio Cestari. @ntoniocp]

@goncy @inproar Buenazo

[Antonio Cestari. @ntoniocp]

@ipla03 @AnasNTy Yeah it depends if you have access to it as a regular const but there could be cases where you configure the query client based on app state.

Also the placement of the query client could vary in SSR scenarios.

Custom hooks don’t have problems with any of the prev

[Antonio Cestari. @ntoniocp]

@ipla03 @AnasNTy It’s not hard too extend the custom hook props with the query options type if you want to receive all query options. Usually you don’t need all, but a few and those are the ones we tend to put in custom hooks. I’d say returning the full result of the query is more useful

[Antonio Cestari. @ntoniocp]

@ipla03 @AnasNTy If you need to access the query client passed in the QueryCache context (to interact with the cache after mutations ) with useQueryClient, you’ll be building a custom hook anyway

[Shreya Shankar @sh_reya]

I’m tired of being “absolutely right!” when coding with an agent

[Antonio Cestari. @ntoniocp]

@fmontes También está la opción de React Router v7 con plugin de Vite (prev Remix) que también es medio sencillo el tema de los loaders

[Antonio Cestari. @ntoniocp]

@fmontes En caso de que ayude, en Next todavía puedes usar el Pages router que es mucho más sencillo/intuitivo para SSR y en Vue creo que Nuxt se parece mucho

Lo de los RSCs trae el beneficio más que todo es para streaming de componentes, para SSR clásico, recomendaría el viejo approach

[Antonio Cestari. @ntoniocp]

@jfdelarosa No olvides los aria labels 👀

[Antonio Cestari. @ntoniocp]

@notsky Based on the name of the states, it’s a long form. Just install and use a form lib instead of separate use states. Also if it’s a long form and it’s separated in sections, you can separate each section.

But also…long forms are bad exp too, so maybe it’s bad from the design 🤪

[Antonio Cestari. @ntoniocp]

@matiasbaldanza @fmontes Ambos tienen su espacio, solo me atrevo a decir que flex suele ser mejor default 😆.

También me he encontrado con código “muy inteligente” que trata de usar grid al máximo y se volvía más difícil de iterar, cuando flex era más conveniente

[Antonio Cestari. @ntoniocp]

@matiasbaldanza @fmontes Si si, total. Si tienes las pautas de número de ítems por fila y eso, tiene sentido. Son menos casos, eso sí. Probablemente layouts de contenido fijo, etc. Y para tablas, que es otro uso, seguramente vale la pena explorar libs ya listas con los roles y demás