Prefer explicit type guards and null checks over TypeScript’s type assertions (as) when handling potentially null or undefined values. Type assertions bypass TypeScript’s type checking system and can lead to runtime errors.

Instead:

Use nullish coalescing operator (??) to provide default values
Implement explicit type guards with Array.isArray() and property checks
Use type predicates for more complex validations

Example (Before):

const menuPlugins = (useConfig("plugins_extra_menu_items") as Array<ExternalViewResponse>) ?? [];

Example (After):

const menuItems = useConfig("plugins_extra_menu_items");
const menuPlugins = Array.isArray(menuItems) ? menuItems : [];

// Or with additional type validation:
if (
  Array.isArray(menuItems) &&
  menuItems.every(item => "name" in item && "href" in item)
) {
  // Safe to use menuItems here
}

This approach ensures runtime safety beyond compile-time type checking and reduces the risk of unexpected null reference exceptions.

Add Repository

Private Repository