From c443ff4d7c730ce12a0b1ee71aa891f2d4627f48 Mon Sep 17 00:00:00 2001 From: Vineeth Kashyap Date: Sun, 3 Nov 2024 20:21:12 -0500 Subject: [PATCH] Add a link to enum compatibilty rules (#690) --- .../pages/en/build/smart-contracts/book/package-upgrades.mdx | 1 + 1 file changed, 1 insertion(+) diff --git a/apps/nextra/pages/en/build/smart-contracts/book/package-upgrades.mdx b/apps/nextra/pages/en/build/smart-contracts/book/package-upgrades.mdx index a8ac36f0d..32566a89b 100644 --- a/apps/nextra/pages/en/build/smart-contracts/book/package-upgrades.mdx +++ b/apps/nextra/pages/en/build/smart-contracts/book/package-upgrades.mdx @@ -85,6 +85,7 @@ published previously need to be compatible and follow the rules below: argument names can change. - `public(friend)` functions are treated as private and thus their signature can arbitrarily change. This is safe as only modules in the same package can call friend functions anyway, and they need to be updated if the signature changes. +- [Enum type upgrade compatibility rules](enums.mdx#enum-type-upgrade-compatibility). When updating your modules, if you see an incompatible error, make sure to check the above rules and fix any violations.