Skip to content

[Fix] Blank continue action when revisiting a saved Slack setup#299

Merged
daniel-lxs merged 1 commit into
developfrom
fix/slack-saved-setup-continue-button
Jul 13, 2026
Merged

[Fix] Blank continue action when revisiting a saved Slack setup#299
daniel-lxs merged 1 commit into
developfrom
fix/slack-saved-setup-continue-button

Conversation

@daniel-lxs

@daniel-lxs daniel-lxs commented Jul 13, 2026

Copy link
Copy Markdown
Member

Problem

The setup auth step renders the filled-in Slack credential fields but nothing below them — no way to continue, in Chrome and Safari alike. Reads as a "blank page" below the form.

Root cause

Two conditions that must mirror each other drifted apart in e36f573:

  • SlackSetupExperience shows its intro screen (which owns the Create Slack app / Enter values manually / Back buttons) only when !showManualSlackValues && !runtimeSatisfied && !savedSatisfied.
  • StepAuthEnvVars suppresses its own action button whenever providerOwnsActions is true — but that check was missing the !savedSatisfied clause.

So with Slack already configured (savedSatisfied), the intro is skipped and the value form is shown, yet StepAuthEnvVars still believes the intro owns the actions → no button rendered anywhere, user is stranded. Deterministic, hence identical in every browser.

Fix

Add the missing !selectedProvider.savedSatisfied clause to providerOwnsActions, with a comment tying it to the intro guard it must stay in sync with. The saved-Slack revisit now renders an enabled Continue button.

Verification

  • New regression test (saved-Slack revisit) fails without the fix, passes with it
  • StepAuthEnvVars.client.test.tsx: 17/17 pass
  • @roomote/web typecheck clean

🤖 Generated with Claude Code

SlackSetupExperience's intro screen owns the step action buttons, and it
is skipped when the Slack config is already saved (savedSatisfied). But
StepAuthEnvVars's providerOwnsActions check was missing the matching
!savedSatisfied clause, so revisiting the auth step with saved Slack
credentials rendered the value form with no action button at all,
stranding the user on the page.

Align providerOwnsActions with the intro guard and add a regression
test for the saved-Slack revisit path.

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
@roomote-roomote

roomote-roomote Bot commented Jul 13, 2026

Copy link
Copy Markdown
Contributor

No code issues found. See task

The fix correctly adds the missing !savedSatisfied clause to providerOwnsActions so it exactly mirrors SlackSetupExperience's intro guard (!showManualSlackValues && !runtimeSatisfied && !savedSatisfied). Verified there is no duplicate button, since the value form (GenericSetupExperience) renders no action button of its own. The added regression test is well-targeted and the full StepAuthEnvVars suite passes (17/17).

Reviewed c2503a5

@daniel-lxs
daniel-lxs merged commit e4fd61e into develop Jul 13, 2026
17 checks passed
@daniel-lxs
daniel-lxs deleted the fix/slack-saved-setup-continue-button branch July 13, 2026 22:21
brunobergher pushed a commit that referenced this pull request Jul 14, 2026
SlackSetupExperience's intro screen owns the step action buttons, and it
is skipped when the Slack config is already saved (savedSatisfied). But
StepAuthEnvVars's providerOwnsActions check was missing the matching
!savedSatisfied clause, so revisiting the auth step with saved Slack
credentials rendered the value form with no action button at all,
stranding the user on the page.

Align providerOwnsActions with the intro guard and add a regression
test for the saved-Slack revisit path.

Co-authored-by: Claude Opus 4.8 <noreply@anthropic.com>
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.

1 participant