canopy-v24-migration

Apply Canopy v23 to v24 breaking changes to Angular projects.

23|46|Updated Sep 7, 2020
One-click install
npx skills add https://github.com/Legal-and-General/canopy --skill canopy-v24-migration
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: canopy-v24-migration
Source: https://github.com/Legal-and-General/canopy/tree/main/skills/canopy-v24-migration
Command: npx skills add https://github.com/Legal-and-General/canopy --skill canopy-v24-migration

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Canopy v23→v24 introduces breaking changes and upgrade gaps that require coordinated updates across icon references, TypeScript typings, and verification steps in Angular projects. This content outlines a structured approach to apply these changes safely and efficiently.

Core Features & Use Cases

  • Automated migration guidance for Canopy v23→v24 breaking changes, including icon name updates and TS symbol adjustments.
  • Clear use cases for upgrading Canopy in existing Angular applications and resolving upgrade-time errors.
  • Step-by-step verification and post-migration checks to ensure a clean, working project after the upgrade.

Quick Start

Run the migration workflow to apply the v23→v24 changes to your Angular project.

Frequently Asked Questions about canopy-v24-migration

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I migrate Canopy v23 to v24 in my Angular project?

Automating the Canopy v24 migration applies the necessary breaking changes to your Angular project, handling UI icon rename mappings, updating TypeScript symbols, and running verification steps to ensure a clean upgrade.

Why does upgrading Canopy to v24 cause TypeScript errors?

Upgrading Canopy to v24 introduces breaking changes to TypeScript typings and symbol names, causing compilation errors that require automated updates to your Angular project's codebase to resolve.

What is the best way to fix broken UI icon references after a Canopy upgrade?

Fixing broken UI icon references after a Canopy upgrade requires applying the v24 icon rename mappings, which automatically updates outdated icon names to the new v24 standard across your Angular components.

Do I need to manually verify my Angular project after migrating Canopy to v24?

Yes, you need to run post-migration verification checks to ensure your Angular project is clean and working after the v24 upgrade, although the process automates applying the TypeScript and icon rename updates.

Can I use an automated tool for Canopy v23 to v24 breaking changes?

Yes, an automated migration workflow can apply Canopy v23 to v24 breaking changes, handling UI icon rename mapping, TypeScript name updates, and verification steps to safely upgrade your Angular project.