Conversation
The manifest declares setUp as a hideable control. When the dashboard names it on the iframe URL, the gear is removed before first paint, the click handler refuses to enter the setup view, and the empty state drops its "Choose Set up" hint. Marking steps done stays on the board. No hide param hides nothing, so an older dashboard and a direct load behave as before.
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
2 participants
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.
Routines declares
setUpas a hideable control. Under the gate the gear is removed before first paint and the switch into setup mode returns early, so create, retire, remove and add step are unreachable; marking steps done is untouched.hideis read at parse time, TastyTiles shape; no param hides nothing.Verified with and without the param on our production display.