Skip to content

Only write non-default shortcuts during migration

Nicolas Fella requested to merge work/nico/migrate-shortcut-non-default into master

When the new component has a different default than the old one we would write the old value, overriding the default

Arguably if the value was never changed it should make use of the new default, so only write an explicit value if the old one is non-default

Merge request reports