Skip to content

[6.x] Apply regenerate handle pattern for replicator sections#14745

Merged
jasonvarga merged 3 commits into
6.xfrom
regen-pattern-for-replicator-handles
Jun 3, 2026
Merged

[6.x] Apply regenerate handle pattern for replicator sections#14745
jasonvarga merged 3 commits into
6.xfrom
regen-pattern-for-replicator-handles

Conversation

@jaygeorge
Copy link
Copy Markdown
Contributor

Description of the Problem

I noticed that while changing some set names – I inadvertently "deleted" the content too because it changed the handle at the same time. Changing the display name should not also change the handle name, and we should use the same "regenerate handle" pattern we use elsewhere.

What this PR Does

  • Applies the regenerate handle pattern to replicator set names and tab names

Before

2026-05-29 at 11 02 30@2x

After

2026-05-29 at 11 01 11@2x

How to Reproduce

  1. Add a replicator field and some dummy sets
  2. Save
  3. Go back in to edit the replicator sets
  4. Change the Display name
  5. Observe how the handle also changes as you change the Display name

jaygeorge and others added 3 commits May 29, 2026 10:44
… that you don't accidentally change the handle when editing the name
Re-introduces handleSyncedWithDisplay, but sets it in edit() rather than
created() so existing items always open with sync disabled. New items with
placeholder handles still get the live sync UX. Also restores the empty-
handle safety net in editConfirmed() for both files.

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
@jasonvarga jasonvarga merged commit 8b02ee0 into 6.x Jun 3, 2026
18 checks passed
@jasonvarga jasonvarga deleted the regen-pattern-for-replicator-handles branch June 3, 2026 20:02
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants