Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

fix(editor): Never show Pinned Data Callout for Input Panel #12446

Open
wants to merge 2 commits into
base: master
Choose a base branch
from

Conversation

CharlieKolb
Copy link
Contributor

@CharlieKolb CharlieKolb commented Jan 3, 2025

Summary

Always hide the banner if we're in the input panel.

Related Linear tickets, Github issues, and Community forum posts

https://linear.app/n8n/issue/ADO-3061/pinned-data-notice-appearing-in-input-pane

Review / Merge checklist

  • PR title and summary are descriptive. (conventions)
  • Docs updated or follow-up ticket created.
  • Tests included.
  • PR Labeled with release/backport (if the PR is an urgent fix that needs to be backported)

@CharlieKolb CharlieKolb marked this pull request as ready for review January 3, 2025 13:46
@@ -1277,7 +1277,12 @@ defineExpose({ enterEditMode });
<template>
<div :class="['run-data', $style.container]" @mouseover="activatePane">
<N8nCallout
v-if="pinnedData.hasData.value && !editMode.enabled && !isProductionExecutionPreview"
v-if="
Copy link
Contributor

Choose a reason for hiding this comment

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

Thank you for the quick fix. Can you please add a test?

Copy link
Contributor Author

@CharlieKolb CharlieKolb Jan 3, 2025

Choose a reason for hiding this comment

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

This wasn't really a bug, but rather a change in (semi-)intended behavior.

I can add tests for the callout banner in general (we don't have any, only for the pin button), but it's probably best logistically to separate that into a tech debt ticket.

Copy link
Contributor

Choose a reason for hiding this comment

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

Luckily we already have good coverage for RunData. Can we simply add a unit test for this there?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

It turns out the input panel has a snapshot test, I have pushed a change to update that. It will catch this showing up accidentally. (This also means the change was more or less intentional on our end back then, since we explicitly updated the snapshot, so just some miscommunication.)

Copy link
Contributor

Choose a reason for hiding this comment

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

It would be nice to have a clear check if there's no pinned data callout in panel, to avoid this bug being reintroduced. Because snapshots don't convey those requirements and get updated often without full consideration/review.

@n8n-assistant n8n-assistant bot added n8n team Authored by the n8n team ui Enhancement in /editor-ui or /design-system labels Jan 3, 2025
Copy link

codecov bot commented Jan 3, 2025

Codecov Report

All modified and coverable lines are covered by tests ✅

📢 Thoughts on this report? Let us know!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
n8n team Authored by the n8n team ui Enhancement in /editor-ui or /design-system
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants