chore: improve monitoring for fix: add defensive null check for objects field in

Added a `console.error` log in `useLoadStaleMetadataEntities.ts` that fires when the `ObjectMetadataItems` query returns a response without the expected `objects` field. This log will appear in Sentry breadcrumbs (as a console error-level breadcrumb) before any downstream TypeError, providing critical diagnostic context: whether `result.data` itself was defined, and flagging the unexpected response shape. This follows the same defensive pattern already used elsewhere in the same file (e.g., `isDefined(result.data?.getPageLayouts)` check on line 138, `isDefined(result.data?.findManyLogicFunctions)` on line 166). The metadata objects query was the only fetch in this file lacking such a guard.
fix: add defensive null check for objects field in metadata query response
2026-03-18 00:31:30 +00:00 · 2026-03-18 00:31:30 +00:00
2 changed files with 8 additions and 1 deletions
@@ -72,6 +72,13 @@ export const useLoadStaleMetadataEntities = () => {
              fetchPolicy: 'network-only',
            })
            .then((result) => {
+              if (!isDefined(result.data?.objects)) {
+                console.error(
+                  'ObjectMetadataItems query returned unexpected response shape',
+                  { hasData: isDefined(result.data) },
+                );
+              }
+
              const compositeObjects =
                mapPaginatedObjectMetadataItemsToObjectMetadataItems({
                  pagedObjectMetadataItems: result.data,
@@ -15,7 +15,7 @@ export const mapPaginatedObjectMetadataItemsToObjectMetadataItems = ({
    ObjectMetadataItem,
    'readableFields' | 'updatableFields'
  >[] =
-    pagedObjectMetadataItems?.objects.edges.map((object) => {
+    pagedObjectMetadataItems?.objects?.edges?.map((object) => {
      const labelIdentifierFieldMetadataId =
        objectMetadataItemSchema.shape.labelIdentifierFieldMetadataId.parse(
          object.node.labelIdentifierFieldMetadataId,