chore: Adding debounce to onValueChange for input widgets
#40849
Conversation
WalkthroughThis change introduces internal state management and debounced input handling for several input-related widgets. Each widget now maintains its own Changes
Sequence Diagram(s)sequenceDiagram
participant User
participant Widget
participant MetaProps
User->>Widget: Type input
Widget->>Widget: Update internal inputValue state
Widget-->>User: UI updates immediately
Widget->>Widget: Start debounce timer (300ms)
Note over Widget: User may continue typing<br>debounce resets
Widget->>MetaProps: (After 300ms) Update meta properties & trigger events
Assessment against linked issues
Suggested labels
Suggested reviewers
Poem
✨ Finishing Touches
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. 🪧 TipsChatThere are 3 ways to chat with CodeRabbit:
SupportNeed help? Create a ticket on our support page for assistance with any issues or questions. Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments. CodeRabbit Commands (Invoked using PR comments)
Other keywords and placeholders
Documentation and Community
|
|
/build-deploy-preview skip-tests=true |
|
Deploying Your Preview: https://github.com/appsmithorg/appsmith/actions/runs/15416479456. |
There was a problem hiding this comment.
Actionable comments posted: 3
📜 Review details
Configuration used: .coderabbit.yaml
Review profile: CHILL
Plan: Pro
📒 Files selected for processing (1)
app/client/src/widgets/BaseInputWidget/component/index.tsx(8 hunks)
⏰ Context from checks skipped due to timeout of 90000ms (8)
- GitHub Check: perform-test / rts-build / build
- GitHub Check: perform-test / server-build / server-unit-tests
- GitHub Check: perform-test / client-build / client-build
- GitHub Check: client-unit-tests / client-unit-tests
- GitHub Check: client-lint / client-lint
- GitHub Check: client-check-cyclic-deps / check-cyclic-dependencies
- GitHub Check: client-build / client-build
- GitHub Check: client-prettier / prettier-check
🔇 Additional comments (4)
app/client/src/widgets/BaseInputWidget/component/index.tsx (4)
12-12: LGTM!The debounce import is correctly added for the new functionality.
489-491: LGTM!The event handlers correctly update the internal state immediately for UI responsiveness while debouncing the actual value change callback.
Also applies to: 494-496
579-579: LGTM!All input components consistently use the internal
inputValuestate, which is necessary for the debouncing mechanism to work correctly.Also applies to: 601-601, 630-630
778-778: LGTM!The interface is correctly updated to include the new state property.
|
Deploy-Preview-URL: https://ce-40849.dp.appsmith.com |
|
/build-deploy-preview skip-tests=true |
|
Deploying Your Preview: https://github.com/appsmithorg/appsmith/actions/runs/15418443754. |
|
Deploy-Preview-URL: https://ce-40849.dp.appsmith.com |
…o chore/debounce-input-change
There was a problem hiding this comment.
Actionable comments posted: 2
🧹 Nitpick comments (7)
app/client/src/widgets/wds/WDSPhoneInputWidget/widget/index.tsx (1)
241-258: Debounced updates implemented correctly.The 300ms delay should effectively batch updates and reduce API calls. Consider making this delay configurable in the future if different widgets need different responsiveness.
app/client/src/widgets/InputWidgetV2/widget/index.tsx (1)
21-21: Consider the static analysis warning about toString.While importing
toStringfrom lodash works, it shadows the globaltoStringproperty. Since you're not using it in this file, consider removing it from the imports to avoid confusion.-import { debounce, isNil, isNumber, merge, toString } from "lodash"; +import { debounce, isNil, isNumber, merge } from "lodash";🧰 Tools
🪛 Biome (1.9.4)
[error] 21-21: Do not shadow the global "toString" property.
Consider renaming this variable. It's easy to confuse the origin of variables when they're named after a known global.
(lint/suspicious/noShadowRestrictedNames)
app/client/src/widgets/wds/WDSInputWidget/widget/index.tsx (1)
208-231: Consider making the debounce delay configurable.The 300ms delay works well for most cases, but different use cases might benefit from different delays. Consider extracting this as a configurable constant or prop in the future.
app/client/src/widgets/InputWidget/widget/index.tsx (1)
898-910: Note the TODO about converting text to derived property.The comment indicates future refactoring plans. This debounced approach will need adjustment when text becomes a derived property for List widget compatibility.
app/client/src/widgets/RichTextEditorWidget/widget/index.tsx (1)
1-625: Consider extracting the debouncing pattern into a reusable hook.Since this exact pattern is duplicated across multiple input widgets (InputWidget, WDSInputWidget, RichTextEditor, and others mentioned in the PR), consider creating a custom hook like
useDebounedInputto reduce code duplication and ensure consistency.Example implementation:
function useDebouncedInput( initialValue: string, externalValue: string, onDebouncedChange: (value: string) => void, delay: number = 300 ) { const [inputValue, setInputValue] = useState(initialValue); const debouncedChange = useMemo( () => debounce(onDebouncedChange, delay), [onDebouncedChange, delay] ); useEffect(() => { setInputValue(externalValue); debouncedChange.cancel(); }, [externalValue]); useEffect(() => { return () => debouncedChange.cancel(); }, []); const handleChange = useCallback((value: string) => { setInputValue(value); debouncedChange(value); }, [debouncedChange]); return [inputValue, handleChange] as const; }app/client/src/widgets/PhoneInputWidget/widget/index.tsx (1)
427-443: Consider making debounce delay configurableThe 300ms delay is hardcoded. Different use cases might benefit from different delays.
Consider extracting the delay as a constant or making it configurable:
+const DEBOUNCE_DELAY = 300; + debouncedOnValueChange = debounce((value: string) => { this.props.updateWidgetMetaProperty( "value", parseIncompletePhoneNumber(value), ); this.props.updateWidgetMetaProperty("text", value, { triggerPropertyName: "onTextChanged", dynamicString: this.props.onTextChanged, event: { type: EventType.ON_TEXT_CHANGE, }, }); if (!this.props.isDirty) { this.props.updateWidgetMetaProperty("isDirty", true); } -}, 300); +}, DEBOUNCE_DELAY);app/client/src/widgets/CurrencyInputWidget/widget/index.tsx (1)
528-541: Consider extracting debounce delay constantSame as PhoneInputWidget, the 300ms delay should be configurable or at least extracted as a constant for maintainability.
📜 Review details
Configuration used: .coderabbit.yaml
Review profile: CHILL
Plan: Pro
📒 Files selected for processing (8)
app/client/src/widgets/CurrencyInputWidget/widget/index.tsx(7 hunks)app/client/src/widgets/InputWidget/widget/index.tsx(5 hunks)app/client/src/widgets/InputWidgetV2/widget/index.tsx(6 hunks)app/client/src/widgets/PhoneInputWidget/widget/index.tsx(7 hunks)app/client/src/widgets/RichTextEditorWidget/widget/index.tsx(5 hunks)app/client/src/widgets/wds/WDSCurrencyInputWidget/widget/index.tsx(6 hunks)app/client/src/widgets/wds/WDSInputWidget/widget/index.tsx(6 hunks)app/client/src/widgets/wds/WDSPhoneInputWidget/widget/index.tsx(6 hunks)
🧰 Additional context used
🧬 Code Graph Analysis (1)
app/client/src/widgets/InputWidget/widget/index.tsx (1)
app/client/src/widgets/BaseWidget.tsx (1)
WidgetState(453-453)
🪛 Biome (1.9.4)
app/client/src/widgets/InputWidgetV2/widget/index.tsx
[error] 21-21: Do not shadow the global "toString" property.
Consider renaming this variable. It's easy to confuse the origin of variables when they're named after a known global.
(lint/suspicious/noShadowRestrictedNames)
app/client/src/widgets/wds/WDSInputWidget/widget/index.tsx
[error] 2-2: Do not shadow the global "toString" property.
Consider renaming this variable. It's easy to confuse the origin of variables when they're named after a known global.
(lint/suspicious/noShadowRestrictedNames)
⏰ Context from checks skipped due to timeout of 90000ms (8)
- GitHub Check: perform-test / client-build / client-build
- GitHub Check: perform-test / server-build / server-unit-tests
- GitHub Check: perform-test / rts-build / build
- GitHub Check: client-check-cyclic-deps / check-cyclic-dependencies
- GitHub Check: client-lint / client-lint
- GitHub Check: client-prettier / prettier-check
- GitHub Check: client-unit-tests / client-unit-tests
- GitHub Check: client-build / client-build
🔇 Additional comments (31)
app/client/src/widgets/wds/WDSPhoneInputWidget/widget/index.tsx (4)
24-37: State management looks good.The addition of the internal state interface and initialization properly manages the input value locally, allowing for immediate UI updates while deferring meta property updates.
183-189: Proper synchronization with external prop changes.Good implementation of canceling pending debounced calls when the value is updated externally. This prevents race conditions and stale updates.
224-227: Essential cleanup on unmount.Canceling the debounced function prevents memory leaks and side effects after the component unmounts.
259-271: Clean separation of UI updates from meta updates.The immediate state update ensures responsive UI while the debounced function handles the meta property updates, effectively addressing the multiple API calls issue.
Also applies to: 328-328
app/client/src/widgets/InputWidgetV2/widget/index.tsx (4)
302-313: State management properly implemented.The internal state structure and initialization follow the same pattern as other input widgets, ensuring consistency across the codebase.
714-719: Lifecycle method correctly handles prop synchronization.Good implementation of state synchronization and cleanup of pending debounced calls when the input value is updated externally.
746-773: Debounced updates with proper cleanup.Good implementation with helpful context about why
textisn't a derived property. The cleanup incomponentWillUnmountprevents memory leaks.
775-778: UI responsiveness maintained with debounced meta updates.The separation of immediate state updates from debounced meta property updates ensures a responsive user experience while reducing API calls.
Also applies to: 813-813
app/client/src/widgets/wds/WDSCurrencyInputWidget/widget/index.tsx (4)
34-45: State management follows established pattern.Good consistency with other input widgets while maintaining the currency input's specific initialization from
rawText.
163-196: Lifecycle methods properly handle cleanup and synchronization.The implementation correctly maintains currency-specific logic while adding the debounced update pattern. Good cleanup in both
componentDidUpdateandcomponentWillUnmount.
197-212: Debounced function correctly handles raw and formatted values.Good separation of concerns by passing both the raw value and formatted value to the debounced function, maintaining the widget's dual-value nature.
213-233: Currency formatting preserved with debounced updates.The implementation successfully maintains decimal limiting and formatting logic while adding the debounce pattern. Good error handling with telemetry capture.
Also applies to: 349-349
🧰 Tools
🪛 Biome (1.9.4)
[error] 218-218: Change to an optional chain.
Unsafe fix: Change to an optional chain.
(lint/complexity/useOptionalChain)
app/client/src/widgets/wds/WDSInputWidget/widget/index.tsx (6)
2-2: Import looks good.The
debounceimport from lodash is appropriate for the debouncing functionality being added.🧰 Tools
🪛 Biome (1.9.4)
[error] 2-2: Do not shadow the global "toString" property.
Consider renaming this variable. It's easy to confuse the origin of variables when they're named after a known global.
(lint/suspicious/noShadowRestrictedNames)
18-30: State management implementation is well-structured.The internal state for
inputValueprovides proper decoupling between UI updates and meta property changes. Good use of nullish coalescing for the fallback value.
170-175: Excellent handling of prop synchronization.The cancellation of pending debounced calls when props change externally prevents race conditions and stale updates. This ensures data consistency.
204-207: Good cleanup practice.Canceling debounced calls on unmount prevents memory leaks and potential errors from updates after component destruction.
232-235: Clean separation of concerns.Immediate state update ensures responsive UI while debounced meta updates reduce unnecessary API calls.
256-259: Correct use of internal state for rendering.Using the internal
inputValuestate ensures immediate UI updates without waiting for prop updates.app/client/src/widgets/InputWidget/widget/index.tsx (3)
158-169: Lifecycle methods properly implemented.State synchronization and cleanup follow the same robust pattern as other input widgets.
912-915: Consistent implementation of value change handler.Follows the established pattern for immediate UI updates with debounced meta updates.
992-999: Proper state usage in formatting logic.All value references correctly use the internal
inputValuestate, ensuring consistent display even during debounced updates.app/client/src/widgets/RichTextEditorWidget/widget/index.tsx (4)
52-66: State management consistent with other input widgets.The RichTextEditor follows the same internal state pattern for managing input values.
506-522: Lifecycle methods handle RTE-specific logic well.The implementation maintains the debouncing pattern while properly handling the widget's
defaultTextandisDirtystate management.
523-540: Debouncing implementation adapted for RTE.The implementation correctly handles the RichTextEditor's state updates with the same debouncing benefits.
562-566: Render correctly uses internal state.The markdown conversion is properly applied to the internal state value before rendering.
app/client/src/widgets/PhoneInputWidget/widget/index.tsx (3)
87-100: State initialization looks goodThe internal state management pattern is correctly implemented with proper initialization from props.
369-375: Proper state synchronization with external updatesGood implementation of syncing internal state when props change externally and canceling pending debounced calls to prevent stale updates.
410-413: Correct cleanup on unmountProperly canceling debounced calls prevents memory leaks and unexpected behavior.
app/client/src/widgets/CurrencyInputWidget/widget/index.tsx (3)
157-168: Consistent state management implementationGood implementation following the same pattern as PhoneInputWidget.
469-474: Proper state sync and cleanupCorrectly handles external prop changes and cancels pending debounced calls.
650-650: Good null safety handlingUsing nullish coalescing operator ensures the value is always a string.
…o chore/debounce-input-change
app/client/cypress/e2e/Regression/ClientSide/Widgets/Input/Inputv2_spec.js
Outdated
Show resolved
Hide resolved
app/client/cypress/e2e/Regression/ClientSide/Widgets/ListV2/Listv2_BasicClientSideData_spec.js
Outdated
Show resolved
Hide resolved
There was a problem hiding this comment.
Actionable comments posted: 0
🧹 Nitpick comments (3)
app/client/src/widgets/InputWidgetV2/widget/index.tsx (1)
21-21: Address the shadowing of globaltoStringproperty.The static analysis tool correctly identifies that importing
toStringfrom lodash shadows the globaltoStringproperty, which can lead to confusion about the origin of the function.Consider using a more specific import or aliasing:
-import { debounce, isNil, isNumber, merge, toString } from "lodash"; +import { debounce, isNil, isNumber, merge, toString as toStr } from "lodash";Then update usage throughout the file from
toStringtotoStr.🧰 Tools
🪛 Biome (1.9.4)
[error] 21-21: Do not shadow the global "toString" property.
Consider renaming this variable. It's easy to confuse the origin of variables when they're named after a known global.
(lint/suspicious/noShadowRestrictedNames)
app/client/src/widgets/wds/WDSInputWidget/widget/index.tsx (1)
2-2: Address the shadowing of globaltoStringproperty.Same issue as in InputWidgetV2 - importing
toStringfrom lodash shadows the global property.Apply the same fix:
-import { debounce, isNumber, merge, toString } from "lodash"; +import { debounce, isNumber, merge, toString as toStr } from "lodash";🧰 Tools
🪛 Biome (1.9.4)
[error] 2-2: Do not shadow the global "toString" property.
Consider renaming this variable. It's easy to confuse the origin of variables when they're named after a known global.
(lint/suspicious/noShadowRestrictedNames)
app/client/src/widgets/CurrencyInputWidget/widget/index.tsx (1)
15-15: Address the shadowing of globaltoStringproperty.Same static analysis issue - the lodash
toStringimport shadows the global property.Apply the same fix as other files:
-import _, { debounce } from "lodash"; +import _, { debounce, toString as toStr } from "lodash";And update any
toStringusage totoStr.
📜 Review details
Configuration used: .coderabbit.yaml
Review profile: CHILL
Plan: Pro
📒 Files selected for processing (13)
app/client/cypress/e2e/Regression/ClientSide/Widgets/Input/Inputv2_spec.js(2 hunks)app/client/cypress/e2e/Regression/ClientSide/Widgets/ListV2/Listv2_BasicClientSideData_spec.js(3 hunks)app/client/cypress/e2e/Regression/ClientSide/Widgets/ListV2/Listv2_Nested_EventBindings_spec.js(3 hunks)app/client/cypress/support/Pages/AggregateHelper.ts(4 hunks)app/client/src/constants/WidgetConstants.tsx(1 hunks)app/client/src/widgets/CurrencyInputWidget/widget/index.tsx(8 hunks)app/client/src/widgets/InputWidget/widget/index.tsx(6 hunks)app/client/src/widgets/InputWidgetV2/widget/index.tsx(7 hunks)app/client/src/widgets/PhoneInputWidget/widget/index.tsx(8 hunks)app/client/src/widgets/RichTextEditorWidget/widget/index.tsx(5 hunks)app/client/src/widgets/wds/WDSCurrencyInputWidget/widget/index.tsx(6 hunks)app/client/src/widgets/wds/WDSInputWidget/widget/index.tsx(6 hunks)app/client/src/widgets/wds/WDSPhoneInputWidget/widget/index.tsx(6 hunks)
✅ Files skipped from review due to trivial changes (2)
- app/client/src/constants/WidgetConstants.tsx
- app/client/cypress/e2e/Regression/ClientSide/Widgets/Input/Inputv2_spec.js
🚧 Files skipped from review as they are similar to previous changes (8)
- app/client/cypress/e2e/Regression/ClientSide/Widgets/ListV2/Listv2_Nested_EventBindings_spec.js
- app/client/cypress/e2e/Regression/ClientSide/Widgets/ListV2/Listv2_BasicClientSideData_spec.js
- app/client/cypress/support/Pages/AggregateHelper.ts
- app/client/src/widgets/wds/WDSCurrencyInputWidget/widget/index.tsx
- app/client/src/widgets/InputWidget/widget/index.tsx
- app/client/src/widgets/PhoneInputWidget/widget/index.tsx
- app/client/src/widgets/wds/WDSPhoneInputWidget/widget/index.tsx
- app/client/src/widgets/RichTextEditorWidget/widget/index.tsx
🧰 Additional context used
🧬 Code Graph Analysis (2)
app/client/src/widgets/InputWidgetV2/widget/index.tsx (3)
app/client/src/widgets/BaseWidget.tsx (1)
WidgetState(453-453)app/client/src/widgets/InputWidget/widget/index.tsx (1)
InputWidgetProps(1114-1156)app/client/src/constants/WidgetConstants.tsx (1)
DEBOUNCE_WAIT_TIME_ON_INPUT_CHANGE(284-284)
app/client/src/widgets/wds/WDSInputWidget/widget/index.tsx (3)
app/client/src/widgets/BaseWidget.tsx (1)
WidgetState(453-453)app/client/src/widgets/InputWidget/widget/index.tsx (1)
InputWidgetProps(1114-1156)app/client/src/constants/WidgetConstants.tsx (1)
DEBOUNCE_WAIT_TIME_ON_INPUT_CHANGE(284-284)
🪛 Biome (1.9.4)
app/client/src/widgets/InputWidgetV2/widget/index.tsx
[error] 21-21: Do not shadow the global "toString" property.
Consider renaming this variable. It's easy to confuse the origin of variables when they're named after a known global.
(lint/suspicious/noShadowRestrictedNames)
app/client/src/widgets/wds/WDSInputWidget/widget/index.tsx
[error] 2-2: Do not shadow the global "toString" property.
Consider renaming this variable. It's easy to confuse the origin of variables when they're named after a known global.
(lint/suspicious/noShadowRestrictedNames)
⏰ Context from checks skipped due to timeout of 90000ms (8)
- GitHub Check: perform-test / rts-build / build
- GitHub Check: perform-test / client-build / client-build
- GitHub Check: perform-test / server-build / server-unit-tests
- GitHub Check: client-unit-tests / client-unit-tests
- GitHub Check: client-lint / client-lint
- GitHub Check: client-check-cyclic-deps / check-cyclic-dependencies
- GitHub Check: client-build / client-build
- GitHub Check: client-prettier / prettier-check
🔇 Additional comments (16)
app/client/src/widgets/InputWidgetV2/widget/index.tsx (7)
305-307: LGTM on the state interface extension.The interface correctly extends
WidgetStatewith theinputValueproperty needed for internal state management.
314-314: Good initialization of internal state.The constructor properly initializes
inputValuefrom theinputTextprop with appropriate fallback to empty string.
717-721: Excellent external prop synchronization logic.The
componentDidUpdateimplementation correctly:
- Syncs internal state when external
inputTextprop changes- Cancels pending debounced calls to prevent stale updates
This ensures the widget stays in sync with external changes while preventing conflicts.
749-751: Good cleanup practice.Properly canceling the debounced function in
componentWillUnmountprevents memory leaks and unwanted updates after unmounting.
754-777: Well-implemented debounced update function.The debounced function correctly:
- Updates meta properties (
text,inputText,isDirty)- Triggers events only when necessary
- Uses the appropriate debounce delay constant
This addresses the core issue of multiple Execute API calls in reactive queries.
779-782: Perfect separation of immediate UI updates and debounced meta updates.The
onValueChangemethod correctly:
- Updates internal state immediately for responsive UI
- Defers meta property updates via debounced function
This approach provides the best of both worlds - immediate visual feedback and optimized API calls.
817-817: Correct usage of internal state for rendering.Using
this.state.inputValueinstead of the prop ensures the input displays the most current user input before meta property updates are processed.app/client/src/widgets/wds/WDSInputWidget/widget/index.tsx (4)
19-21: Consistent state management implementation.The state interface and constructor follow the same solid pattern as InputWidgetV2, appropriately using
rawTextfor the WDS variant.Also applies to: 23-30
171-175: Proper external prop synchronization.Correctly syncs
inputValuewithrawTextprop changes and cancels pending debounced calls, maintaining consistency with the other widget implementations.
205-207: Well-implemented lifecycle management and debounced updates.The cleanup in
componentWillUnmountand the debounced function implementation are consistent with the pattern established in other widgets.Also applies to: 210-232
234-237: Excellent implementation of immediate state updates with debounced meta updates.The
onValueChangeandgetWidgetViewmethods correctly implement the pattern of immediate UI responsiveness with optimized backend updates.Also applies to: 260-260
app/client/src/widgets/CurrencyInputWidget/widget/index.tsx (5)
160-162: Consistent state management for currency input.The state interface and constructor correctly follow the established pattern, appropriately using the
textprop for currency widgets.Also applies to: 168-171
472-476: Proper synchronization with currency text property.The
componentDidUpdatelogic correctly syncs with thetextprop and cancels pending debounced calls, maintaining consistency with other widget implementations.
502-504: Well-implemented debounced updates for currency input.The cleanup and debounced function correctly handle currency-specific meta property updates while following the established pattern.
Also applies to: 532-545
565-566: Excellent integration of currency formatting with debounced updates.The
onValueChangemethod correctly:
- Applies currency-specific formatting (decimal separator handling)
- Updates internal state immediately for UI responsiveness
- Triggers debounced meta property updates
The currency formatting logic is appropriately preserved while implementing the debounce optimization.
654-654: Correct usage of internal state for currency display.Using
this.state.inputValueensures the currency input shows the most current formatted value before meta updates are processed.
…t widgets (#40922) ## Description Reverting the change to add debounce to `onValueChange` for input widgets. (Reverting PR: [#40849](#40849)) Fixes [#40912](#40912) ## Automation /ok-to-test tags="@tag.All" ### 🔍 Cypress test results <!-- This is an auto-generated comment: Cypress test results --> > [!IMPORTANT] > 🟣 🟣 🟣 Your tests are running. > Tests running at: <https://github.com/appsmithorg/appsmith/actions/runs/15583889634> > Commit: 49e570b > Workflow: `PR Automation test suite` > Tags: `@tag.All` > Spec: `` > <hr>Wed, 11 Jun 2025 11:41:27 UTC <!-- end of auto-generated comment: Cypress test results --> ## Communication Should the DevRel and Marketing teams inform users about this change? - [ ] Yes - [ ] No <!-- This is an auto-generated comment: release notes by coderabbit.ai --> ## Summary by CodeRabbit - **Refactor** - Improved input widgets and related components to update values instantly without delay, removing internal state management and debounced input handling. All text and value changes are now immediately reflected in the UI and underlying data. - **Chores** - Updated automated tests to use immediate typing actions, removing artificial delays previously used for input events. <!-- end of auto-generated comment: release notes by coderabbit.ai -->
Description
Adding debounce to
onValueChangefor input widgets to fix multiple Execute API calls happening in reactive queries flow.Fixes #40813
Automation
/ok-to-test tags="@tag.All"
🔍 Cypress test results
Tip
🟢 🟢 🟢 All cypress tests have passed! 🎉 🎉 🎉
Workflow run: https://github.com/appsmithorg/appsmith/actions/runs/15486342735
Commit: 6943ba5
Cypress dashboard.
Tags:
@tag.AllSpec:
Fri, 06 Jun 2025 09:40:52 UTC
Communication
Should the DevRel and Marketing teams inform users about this change?
Summary by CodeRabbit