Skip to content

Leftover Debug Statement Polluting Console in ZoomConfigControl #39622

@iskanderknani2005-oss

Description

@iskanderknani2005-oss

Bug description

Bug description
When using the Explore view as mentioned (here), the application builds and runs normally BUT every time the user drags the Base Width slider inside the ZoomConfigControl panel, the following unwanted output appears in the browser console:

Console Output
'now in onbasewidthcahnge'
triggered on every drag event from:
ZoomConfigControl.tsx:68 (inside onBaseWidthChange)
→ src/explore/components/controls/ZoomConfigControl/ZoomConfigControl.tsx

I identified the root cause and the fix is straightforward. Please apply the changes described below to the codebase.

Short summary

• Root cause: a debug console.log statement was accidentally left inside the onBaseWidthChange() handler before the code was merged. The string contains a typo ('onbasewidthcahnge' instead of 'onbasewidthchange') confirming it was never meant for production.
• Fix: delete the single offending line. No logic is affected.

Screenshots/recordings

Screenshots/recordings
No response

Superset version

5.0.0

Python version

3.9

Node version

16

Browser

Chrome

Additional context

What was changed

  1. Edited: src/explore/components/controls/ZoomConfigControl/ZoomConfigControl.tsx
    • Removed line 68 inside onBaseWidthChange():
    BEFORE:
    const onBaseWidthChange = (width: number) => {
    console.log('now in onbasewidthcahnge');
    setBaseWidth(width);

    AFTER:
    const onBaseWidthChange = (width: number) => {
    setBaseWidth(width);
    Files inspected (for context)

• src/explore/components/controls/ZoomConfigControl/ZoomConfigControl.tsx

Additional context: No other console.log statements were found in the same file. No tests reference this line. Zero functional impact.

Checklist

  • I have searched Superset docs and Slack and didn't find a solution to my problem.
  • I have searched the GitHub issue tracker and didn't find a similar bug report.
  • I have checked Superset's logs for errors and if I found a relevant Python stacktrace, I included it here as text in the "additional context" section.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions