You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently we do not handle the segment union type properly in Gazebo, we only handle the happy path. What happens instead, is that the user sees an entire error page which is not ideal.
The ideal outcome is that we update the GQL queries that call segments field and handle all of the different types, see the screenshot below.
After updating the queries we'll also need to update the zod schemas with a discriminated union type on the __typename field, similar to that of Repository.
Once those two things are done, we'll have to update the respective file diffs to display a custom error messages in these cases.
segments union type:
The text was updated successfully, but these errors were encountered:
Currently we do not handle the segment union type properly in Gazebo, we only handle the happy path. What happens instead, is that the user sees an entire error page which is not ideal.
The ideal outcome is that we update the GQL queries that call
segments
field and handle all of the different types, see the screenshot below.After updating the queries we'll also need to update the zod schemas with a discriminated union type on the
__typename
field, similar to that ofRepository
.Once those two things are done, we'll have to update the respective file diffs to display a custom error messages in these cases.
segments
union type:The text was updated successfully, but these errors were encountered: