Alessandro

I love how the general idea of "complex query" is a fucking JOIN

Using Projections with Declared Queries in spring-data-jdbc · Issue #2127 · spring-projects/spring-data-relational Summary Interface-based projections with nested objects work perfectly with derived query methods but fail when using custom @Query annotations. The error indicates Spring Data JPA cannot instantia...

Another day another banger

github.com/spring-proje...

Moving business logic from services to domain objects looks like a pretty good idea to avoid having anemic models, until you realize there is no way for them to enforce business logic on delete operations 🙃

I hate that every single example on Domain Driven Design aggregates is always Order + Order items.
EVERY SINGLE ONE.
It shouldn't be that hard to make different examples for a design pattern 🤔

I don't like Query by Example or JPA Criteria API with Specifications because they force JPA-specific classes into my repository method parameters. Aren't repository interfaces supposed to abstract away implementation details so you can swap them later?

There is literally zero value added by using spring-data-jdbc.
You cannot achieve the most basic things with it (e.g. querying with some optional search parameters and pagination)

I think there is no reason to prefer react query global onError handler to an axios interceptor

Expo Documentation Build one JavaScript/TypeScript project that runs natively on all your users' devices.

I'm not a fan of video tutorials. Are all the topics of these videos already covered with the same granularity on expo docs.expo.dev?

Tried downloading an older version of Google Translate from 2024. With that the translation works correctly.
Looks like it's a regression from Google side.

can confirm

Using navigation.setOptions({ headerRight }) just to update parts of the header feels counterintuitive. It breaks the declarative component model React encourages. I'd rather just render <Header /> in my JSX and control everything with props/state like normal — it’s clearer and easier to maintain.

I'm slowly arriving at the conclusion that navigation libraries should just focus on routing and nothing else.

non hai idea di quante volte l'ho notato in ufficio.
Da brividi.

meow

Coming from React Native, it's strange to see routes being unmounted and losing their state when navigating.
Being able to go back to a screen with it's state as you left it previously without having to do any fancy state management is fantastic.
Stack navigation is so cool!

context: views with opacity set to 0 do not receive click events on iOS but does on Android.

I'm not sure on how I feel about this 🤔

Migrating to react native New Architecture was not as smooth as I wished

well that escalated quickly! 😂

I'm finding too many issues in common libraries lately

How I Manage Signing Configs with Expo Prebuild I love the idea behind Continuous Native Generation (CNG) and Expo Prebuild. The ability to avoid managing native projects and focus solely…

By the way I wrote a post on the topic:
medium.com/@alessandro....

I understand that expo has its business with EAS but man, having to write my own plugin to set signing config when running expo prebuild feels bad 🫣

is expo trying to kill single page applications?

The Bumpy Road to Implementing a Map in My Expo Universal App | Alessandro In this blog post, I’ll walk you through the journey of displaying a map with markers in my Expo Router app. Was it a smooth, trouble-free experience? Unfortunately, no. I’ll share the challenges I f...

My very first attempt at blogging! 😳
Just some thoughts on how painful it was to use a reactjs library in a basic expo router web version of an app.

whtwnd.com/variabileale...

Is there any active codebase on github using expo-router? 👀

Right now I wrote a proxy in express but I need to remember to start it separately. I'd like a better integrated solution as vite has.

Since @expo/webpack-config is deprecated and no longer receiving feature updates, what is the recommended way to set up a proxy for API requests in an Expo Web project?
Started from mobile, where CORS is not an issue. Now, when running on web, all my API requests fail due to CORS restrictions.

Thinking more about it I'm not so sure anymore. I think there should be an easy way to understand that you tried to navigate to a protected route in order to go back to it after authentication 🤔

KeyboardAvoidingView is basically just trial and error until it works not as you wanted but near that at least.

I don't think I'll use Expo Router in my next project. RN7 static configs look promising and the ability to pass a screen a callback to determine whether the screen should be rendered or not makes auth sooo much easier with a single navigator 👀