Skip to content

fix: show correct header in code-hinter for success message field#16377

Open
Rudolph37 wants to merge 1 commit into
ToolJet:developfrom
Rudolph37:develop
Open

fix: show correct header in code-hinter for success message field#16377
Rudolph37 wants to merge 1 commit into
ToolJet:developfrom
Rudolph37:develop

Conversation

@Rudolph37
Copy link
Copy Markdown

Fix: Show correct header in code-hinter for success message field


Problem

When opening the code-hinter popup for the "Success Message" field in a RunJS query, the popup header displays "Editor" (default value) instead of "Success Message".

Steps to Reproduce

  1. Open a RunJS query in the Query Manager
  2. Click the code-hinter icon on the Success Message field
  3. Observe the popup header shows "Editor" instead of "Success Message"

Expected Behavior

Popup header should display "Success Message".

Root Cause

The componentName prop was not passed to the <CodeHinter> component in SuccessNotificationInputs.jsx, causing it to fall back to the default 'Editor' label.

Fix

Added componentName="Success Message" prop to the <CodeHinter> component.

Files Changed

  • frontend/src/AppBuilder/QueryManager/Components/SuccessNotificationInputs.jsx

Before

<CodeHinter
  type="basic"
  initialValue={options.successMessage}
  onChange={(value) => optionchanged('successMessage', value)}
  placeholder={t('editor.queryManager.queryRanSuccessfully', 'Query ran successfully')}
  cyLabel={'success-message'}
/>

After

<CodeHinter
  type="basic"
  componentName="Success Message"
  initialValue={options.successMessage}
  onChange={(value) => optionchanged('successMessage', value)}
  placeholder={t('editor.queryManager.queryRanSuccessfully', 'Query ran successfully')}
  cyLabel={'success-message'}
/>

Added componentName prop to CodeHinter component to display correct header
@CLAassistant
Copy link
Copy Markdown

CLAassistant commented May 11, 2026

CLA assistant check
All committers have signed the CLA.

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.

2 participants