itamar

for anyone who's recently followed me - here's what you can expect...

@sseraphini @jantimon Sorry for the delay seeing this. Thanks for the feedback. If you haven't already would you mind opening an issue with details on exactly what's being type safety in your app? This will help us understand how to fill that gap.

@jantimon @itamarok I would open more issues to find people with the same problems

@sseraphini do you use relay with @⁠throwOnFieldError? the relay team (especially @itamarok) promote the usage of @⁠throwOnFieldError but it breaks the type-safety of the entire app did you find a way to solve that? github.com/facebook/relay…

@GraphQL thank you for having me! What a community!

Sharing internal insights from Meta regarding Relay error handling helps the Nullability Working Group immensely - thank you @itamarok for all your input & contributions to the WG!!

We’ve just released version 18.2.0 of Relay. This version includes compiler-driven codemods and expanded support for at-catch. github.com/facebook/relay…

Relay 18 is out and I’m really excited about the powerful new new capabilities it enables, so I wanted to share them in a thread! 1/9👇

@rickyfm nit

too many opinions, not enough pull requests

@kmsaldana1 @sachee I am intentionally not saying normalized cache/store because I want to separate the mechanics of how the error is provided from my question - which is what the desired experience is. That said, it can be implemented either at store-time, or at read-time.

@kmsaldana1 @sachee Thanks! I'll update here when it's fully ready to be used. Yeah, so to clarify - I'm not talking about component tree propagation. Rather, each component that's querying this field - should that component see the updated error whether they're the primary querying comp.

In Relay - we're working on explicit errors and error handling - and would love your feedback! When you get a field error - do you expect to break data-consistency to show, for instance, previous valid value? If so, how do you expect to control that behavior?

@kmsaldana1 @sachee So that essentially gives you OOTB behavior like what you currently hand-roll. I think the question is - do we want that union value to propagate to secondary places where the same field is used.

@kmsaldana1 @sachee Yeah, this makes sense. so my @.catch directive in Relay (in development) - would allow you to do that - essentially a response type would be a union of {ok: false, errors: [] } or {ok: true, value: {...}} - and the default is to throw. #relay-error-handling" target="_blank" rel="nofollow noopener">github.com/graphql/graphq…

@StatisticsFTW @StatisticsFTW would you envision these working more or less the same as resolvers? as in ErrorResolver?

@StatisticsFTW Yes, the idea of a callback of some kind to allow more control has come up, for sure.

@tobiastengler @StatisticsFTW Just confirming the two approaches.

@tobiastengler @StatisticsFTW This is interesting. I think when we talk about consistency sometimes we conflate store consistency with presented value consist. For @tobiastengler, store consistency is retained while value scopes to owner, for @StatisticsFTW store is consistent but that carries to the value.

אדמתי בוערת 😢

Israeli friends - if you're stuck in the NY/NJ airports and need hosting, please let me know - we've volunteered to host. ❤️ 🇮🇱

@DaffyWegner רק מוודא שיש לכם איפה להישאר בחו"ל עד שתוכלו לחזור. אם לא - אנחנו פותחים את הבית שלנו בניו ג'רזי.

תושבי הדרום והסביבה אנו נמצאים בחול כרגע ולא נראה שחוזרים בשבוע הקרוב לאור ביטולי טיסות מציעה את הבית שלנו במרכז תל אביב, עם ממ״ד בתוך הבית, ושמירה במתחם. כל מי שצריך - אנא לפנות ונדאג להכל 🇮🇱

I completely forgot this website exists

software engineers, please adhere

I'm going to take a break from social media for a while.