fix(heatmaps): open heatmaps settings section instead of autocapture when configuring#51841
Merged
lricoy merged 1 commit intoPostHog:masterfrom Mar 23, 2026
Merged
Conversation
…when configuring The Configure button on the heatmaps warning banner was opening the Autocapture settings section instead of the Heatmaps section because sectionId was set to 'environment-autocapture' instead of 'environment-heatmaps'. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
Contributor
|
Last reviewed commit: "fix(heatmaps): open ..." |
lricoy
approved these changes
Mar 23, 2026
Member
|
Thanks @phillram |
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.
Problem
When heatmaps aren't enabled on a project, the heatmaps page shows a warning banner with a "Configure" button. Clicking it opens a settings side panel, but it navigates to the Autocapture settings section instead of the Heatmaps section. This is because
sectionIdwas set to'environment-autocapture'instead of'environment-heatmaps'in both warning components.Changes
HeatmapsWarnings.tsx: ChangedsectionIdfrom'environment-autocapture'to'environment-heatmaps'HeatmapsBrowser.tsx(Warningscomponent): Same fixHow did you test this code?
🤖 I'm an agent and haven't tested this manually. The fix was verified by:
environment-heatmapsexists as a valid section inSettingsMap.tsxwith theheatmapssetting IDenvironment-autocapturewithsettingId: 'heatmaps'remainPublish to changelog?
No
Docs update
No docs update needed.
🤖 LLM context
Co-authored by Claude Code (Claude Opus 4.6). The fix was identified by tracing the
openSettingsPanelcall from the warning banner through to the settings map, confirming the section ID mismatch.