Skip to content

fix: avoid using fragment panels#390

Merged
sharanyavinod merged 2 commits intoewfrom
ew-canvas
Apr 24, 2026
Merged

fix: avoid using fragment panels#390
sharanyavinod merged 2 commits intoewfrom
ew-canvas

Conversation

@sharanyavinod
Copy link
Copy Markdown

Previous panel stored as fragment and current implementation are creating duplicates -> fix to avoid using previously stored fragments within canvas

Preview: https://da.live/canvas?nx=ew-panels&nxver=2#/exp-workspace/frescopa/index

@aem-code-sync
Copy link
Copy Markdown

aem-code-sync Bot commented Apr 24, 2026

Hello, I'm the AEM Code Sync Bot and I will run some actions to deploy your branch.
In case there are problems, just click the checkbox below to rerun the respective action.

  • Re-sync branch
Commits

Comment thread nx2/blocks/canvas/canvas.js Outdated
});

// Restore any panels that were open in the previous session.
// Restore panels opened by canvas (no fragment URL). Fragment-based entries are legacy
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I'm not sure I'd call it legacy - other features that use nx might want to use panels with fragments, as that's a common edge delivery pattern. Here it makes more sense if canvas just controls them.

@sharanyavinod sharanyavinod merged commit 0c70a87 into ew Apr 24, 2026
2 checks passed
@sharanyavinod sharanyavinod deleted the ew-canvas branch April 24, 2026 13:18
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