Repository navigation
Conversation
Propagate published state from the host to visualization controls. Hide visualization switching while preserving table exports and rendering published results from the saved graph configuration.
jongyoul
approved these changes
Oct 29, 2026
This branch has not been deployed
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What is this PR for?
The opt-in React published-paragraph view exposes visualization mode buttons that only update local React state. This allows viewers to switch away from the saved visualization, unlike the Angular published view, which hides these editing controls.
This PR propagates the published state from the host through result rendering to
VisualizationControls. Published results use the saved graph configuration and do not expose visualization switching. Table exports remain available, and non-published controls retain their existing behavior.What type of PR is it?
Bug Fix
What is the Jira issue?
How should this be tested?
With frontend dependencies installed and the Zeppelin backend running at
http://localhost:8080, run the following fromzeppelin-web-angular:npm run test:react npm run e2e:fast -- --grep "Published table results"Published paragraphs should hide visualization mode controls while preserving table exports.
Questions: