Guard getResourceStatuses against a null resource

[Valyrian-Code]

Problem

getResourceStatuses(resource, userInfo) in utils/ResourceUtils.js is written to tolerate a missing resource — it guards three reads:

const { executions = [] } = resource || {};
const isApproved = resource?.is_approved;
const isPublished = isApproved && resource?.is_published;

…but then dereferences resource without a guard:

...(resource.advertised === false ? [{ ... }] : []),

So getResourceStatuses(null) (or undefined) throws TypeError: Cannot read properties of null (reading 'advertised'), defeating the null-handling the rest of the function already implements.

Fix

...(resource?.advertised === false ? [{ ... }] : []),

Test

Added to utils/__tests__/ResourceUtils-test.js: getResourceStatuses(null) throws on master and returns the expected status object (isProcessing/isDeleting/isCopying: false, items: []) with the fix. Full suite green.

[Copilot]

Copilot was unable to review this pull request because the user who requested the review has reached their quota limit.

[gemini-code-assist]

Code Review

This pull request introduces optional chaining (resource?.advertised) in the getResourceStatuses utility function to prevent potential runtime errors when the resource parameter is null or undefined. Additionally, a unit test has been added to verify that the function handles a null resource gracefully and returns the expected default statuses. There are no review comments to address, and the changes look correct and well-tested.

Important

The consumer version of Gemini Code Assist on GitHub is being sunset. Starting June 18, 2026, new organization installations will be blocked, and all code review activity will officially cease on July 17, 2026.
For more details on the timeline and next steps, please review the Help Documentation.