Why are Slot Section IDs changing when I update component patterns via CLI?
Last updated: June 16, 2026
Problem Statement
When using Uniform CLI commands to update component patterns, you may notice that Slot Section IDs are being regenerated instead of preserved. This can cause cascading changes in places where the pattern is used, as the system treats these as new components rather than updates to existing ones.
Solution
This issue occurs because the component pattern YAML file is missing the _id property for slot sections, which causes Uniform to generate a new ID every time you push the pattern.
To resolve this issue, you need to include component IDs when pulling pattern data from Uniform:
When using
uniform sync pull, component IDs are automatically includedWhen using specific commands like
uniform canvas component-pattern, you must explicitly add the--componentIDsflag:
uniform canvas component-pattern pull --componentIDs
This ensures that all slot sections and components retain their original IDs when you pull the pattern data, preventing ID regeneration during subsequent push operations.
The --componentIDs flag is essential for maintaining consistency between your local pattern files and the patterns stored in Uniform, avoiding unintended cascading changes across your project.