Files that changed from the base of the PR and between ae97421 and 5f4d092.

• app/client/src/WidgetProvider/factory/index.tsx (2 hunks)
• app/client/src/layoutSystems/anvil/integrations/sagas/anvilDraggingSagas/anvilDraggingSagas.test.ts (2 hunks)
• app/client/src/layoutSystems/anvil/integrations/sagas/anvilDraggingSagas/helpers.ts (1 hunks)
• app/client/src/layoutSystems/anvil/integrations/sagas/anvilDraggingSagas/index.ts (3 hunks)
• app/client/src/layoutSystems/anvil/integrations/sagas/anvilWidgetAdditionSagas/helpers.ts (1 hunks)
• app/client/src/layoutSystems/anvil/integrations/sagas/anvilWidgetAdditionSagas/index.ts (1 hunks)
• app/client/src/layoutSystems/anvil/integrations/sagas/index.ts (2 hunks)
• app/client/src/layoutSystems/anvil/utils/layouts/update/mainCanvasLayoutUtils.ts (2 hunks)
• app/client/src/layoutSystems/anvil/utils/layouts/update/sectionUtils.ts (3 hunks)
• app/client/src/layoutSystems/anvil/utils/layouts/update/zoneUtils.ts (4 hunks)
• app/client/src/layoutSystems/anvil/utils/sectionOperationUtils.ts (2 hunks)
• app/client/src/layoutSystems/anvil/utils/widgetAdditionUtils.ts (2 hunks)
• app/client/src/sagas/WidgetAdditionSagas.ts (5 hunks)
• app/client/src/widgets/anvil/ZoneWidget/widget/config/defaultConfig.ts (1 hunks)
• app/client/src/widgets/wds/WDSInputWidget/config/defaultsConfig.ts (1 hunks)
• app/client/src/widgets/wds/WDSModalWidget/config/defaultsConfig.ts (1 hunks)
• app/client/src/widgets/wds/WDSTableWidget/config/defaultsConfig.ts (1 hunks)

• app/client/src/widgets/wds/WDSModalWidget/config/defaultsConfig.ts

app/client/src/widgets/wds/WDSInputWidget/config/defaultsConfig.ts (1)

9-9: Verify the implications of changing the version from 2 to 1.

Changing the version property from 2 to 1 might have broader implications on how the widget behaves or is rendered. Ensure that this change is backward compatible and does not introduce any regressions.

app/client/src/layoutSystems/anvil/integrations/sagas/index.ts (2)

17-17: LGTM! Ensure the new saga does not introduce side effects.

The code changes are approved.

However, ensure that the new saga does not introduce any unintended side effects or conflicts with existing sagas.

---

8-8: Ensure proper implementation and integration of anvilWidgetAdditionSagas.

The addition of anvilWidgetAdditionSagas modifies the control flow and allows it to run concurrently with existing sagas. Verify that this new saga is correctly implemented and integrated.

Verification successful

Let's correct the previous command and gather the necessary information to verify the implementation and integration of anvilWidgetAdditionSagas.

---

The implementation and integration of anvilWidgetAdditionSagas are correct.

The anvilWidgetAdditionSagas is properly defined and integrated into the saga system. It is imported and forked within the anvilSagas function, ensuring it runs concurrently with other sagas.

• File: app/client/src/layoutSystems/anvil/integrations/sagas/index.ts
  • Line: 8
  • Details: The anvilWidgetAdditionSagas is imported and forked within the anvilSagas generator function.
• File: app/client/src/layoutSystems/anvil/integrations/sagas/anvilWidgetAdditionSagas/index.ts
  • Details: The anvilWidgetAdditionSagas function is defined to handle specific action types using takeLatest.

Scripts executed

The following scripts were executed for the analysis:

Script:

#!/bin/bash
# Description: Verify the implementation and integration of `anvilWidgetAdditionSagas`.

# Test: Search for the implementation details of `anvilWidgetAdditionSagas`. Expect: Proper implementation and integration.
rg --type javascript -A 10 $'anvilWidgetAdditionSagas'

Length of output: 88

---

Script:

#!/bin/bash
# Description: Verify the implementation and integration of `anvilWidgetAdditionSagas`.

# Search for the implementation details of `anvilWidgetAdditionSagas`.
rg 'anvilWidgetAdditionSagas' -A 10

# Search for the import statements of `anvilWidgetAdditionSagas` to understand its integration.
rg 'import anvilWidgetAdditionSagas' -A 5

Length of output: 9138

app/client/src/layoutSystems/anvil/integrations/sagas/anvilDraggingSagas/helpers.ts (1)

1-32: Verify the performance and correctness of getMainCanvasLastRowHighlight.

The function getMainCanvasLastRowHighlight retrieves highlighting information for the last row in the main canvas layout. Ensure that the function performs efficiently and returns correct data.

app/client/src/widgets/wds/WDSTableWidget/config/defaultsConfig.ts (1)

39-39: Ensure compatibility with version change.

The version field in the defaultsConfig object has been changed from 2 to 1. This might affect how the application interprets the configuration settings. Ensure that this change does not introduce any incompatibilities or regressions.

app/client/src/widgets/anvil/ZoneWidget/widget/config/defaultConfig.ts (2)

46-60: Good job on handling modal widget hierarchy!

The new logic block correctly processes the widget hierarchy to determine if a widget is contained within a modal. This ensures that modal widgets do not display an elevated background by default, improving visual consistency.

---

33-34: Clarify the purpose of the parent parameter.

The comment questions the necessity of the parent parameter. Ensure that this parameter is indeed required or remove it if it is redundant.

Verification successful

Let's correct the file type and search for the usage of the parent parameter in TypeScript files to determine its necessity.

---

The parent parameter is necessary.

The parent parameter is used extensively across multiple files in the codebase, indicating its importance in the widget system. Removing it could lead to unintended consequences.

• app/client/src/widgets/FormWidget/widget/index.tsx
• app/client/src/widgets/wds/WDSModalWidget/config/defaultsConfig.ts
• app/client/src/widgets/anvil/SectionWidget/widget/config/defaultConfig.ts
• app/client/src/widgets/anvil/ZoneWidget/widget/config/defaultConfig.ts
• app/client/src/widgets/StatboxWidget/widget/index.tsx
• app/client/src/widgets/ListWidgetV2/widget/defaultProps.ts
• app/client/src/widgets/ContainerWidget/widget/index.tsx
• app/client/src/utils/WidgetPropsUtils.tsx
• app/client/src/sagas/WidgetAdditionSagas.ts
• app/client/src/sagas/WidgetBlueprintSagas.ts
• app/client/src/sagas/CanvasSagas/DraggingCanvasSagas.ts
• app/client/src/layoutSystems/autolayout/utils/heightUpdateUtils.ts
• app/client/src/layoutSystems/anvil/utils/paste/mainCanvasPasteUtils.ts
• app/client/src/layoutSystems/anvil/utils/paste/zonePasteUtils.ts
• app/client/src/layoutSystems/anvil/utils/paste/sectionPasteUtils.ts
• app/client/src/layoutSystems/anvil/utils/anvilChecksUtils.ts
• app/client/src/layoutSystems/anvil/utils/paste/destinationUtils/index.ts
• app/client/src/layoutSystems/anvil/utils/paste/utils.ts
• app/client/src/layoutSystems/anvil/integrations/sagas/pasteSagas/index.ts
• app/client/src/layoutSystems/anvil/integrations/sagas/anvilWidgetAdditionSagas/helpers.ts
• app/client/src/WidgetProvider/factory/index.tsx

Scripts executed

The following scripts were executed for the analysis:

Script:

#!/bin/bash
# Description: Verify the usage of the `parent` parameter in the codebase to ensure it is necessary.

# Test: Search for the usage of the `parent` parameter. Expect: Relevant usage or redundancy.
rg --type python -A 5 $'parent: FlattenedWidgetProps'

Length of output: 85

---

Script:

#!/bin/bash
# Description: Verify the usage of the `parent` parameter in the codebase to ensure it is necessary.

# Test: Search for the usage of the `parent` parameter in TypeScript files.
rg --type ts -A 5 'parent: FlattenedWidgetProps'

Length of output: 14937

app/client/src/layoutSystems/anvil/utils/widgetAdditionUtils.ts (1)

1-1: Ensure the logic for creating widget payloads is refactored or relocated.

The getCreateWidgetPayload function has been removed. Ensure that the logic for creating widget payloads has been refactored or relocated appropriately to avoid any issues with widget instantiation.

app/client/src/layoutSystems/anvil/integrations/sagas/anvilDraggingSagas/index.ts (5)

Line range hint 1-17:
Good job on removing unused imports!

This helps in keeping the code clean and maintainable.

---

Line range hint 26-45:
Well-structured function with proper error handling!

The moveWidgetsSaga function is correctly implemented and handles errors appropriately.

---

Line range hint 47-68:
Good use of utility functions!

The handleWidgetMovement function is correctly implemented and uses appropriate utility functions.

---

Line range hint 70-98:
Great job on handling redundant zones!

The handleDeleteRedundantZones function is correctly implemented and uses appropriate utility functions.

---

Line range hint 100-104:
Nice simplification of the default export function!

This helps in keeping the code clean and maintainable.

app/client/src/layoutSystems/anvil/utils/layouts/update/mainCanvasLayoutUtils.ts (4)

Line range hint 1-16:
Necessary import added!

The import statement for addNewAnvilWidgetToDSL is necessary for the updated functionality.

---

29-37: Simplified function and improved performance!

The changes to addDetachedWidgetToMainCanvas simplify the function and improve performance by removing an intermediate function call.

---

Line range hint 39-92:
Well-structured function with appropriate utility functions!

The addWidgetsToMainCanvasLayout function is correctly implemented and uses appropriate utility functions.

---

Line range hint 153-170:
Good job on moving widgets to the main canvas!

The moveWidgetsToMainCanvas function is correctly implemented and uses appropriate utility functions.

app/client/src/layoutSystems/anvil/utils/sectionOperationUtils.ts (2)

Line range hint 1-17:
Necessary import added!

The import statement for getUpdatedListOfWidgetsAfterAddingNewWidget is necessary for the updated functionality.

---

Line range hint 161-176:
Improved widget management!

The changes to addNewZonesToSection indicate a shift in how new widgets are integrated into the existing widget structure, potentially improving the overall responsiveness or correctness of widget management within the application.

app/client/src/layoutSystems/anvil/utils/layouts/update/zoneUtils.ts (5)

Line range hint 26-44:
Good use of the new function addNewAnvilWidgetToDSL.

The changes improve readability and maintainability by using an object format for parameters.

However, ensure that the new function is correctly integrated and tested.

Verification successful

---

Good integration of the function addNewAnvilWidgetToDSL.

The function is consistently used across multiple modules, improving readability and maintainability. Ensure the function implementation in helpers.ts is correct.

Scripts executed

The following scripts were executed for the analysis:

Script:

#!/bin/bash
# Description: Verify the integration of `addNewAnvilWidgetToDSL`.

# Test: Search for the function definition and its usage. Expect: Correct integration and usage.
rg --type ts -A 5 $'addNewAnvilWidgetToDSL'

Length of output: 7550

---

179-183: Good use of the new function addNewAnvilWidgetToDSL.

The changes improve readability and maintainability by using an object format for parameters.

However, ensure that the new function is correctly integrated and tested.

Verification successful

---

The integration of addNewAnvilWidgetToDSL appears to be consistent and correct across the codebase.

The function is imported and utilized in multiple files, maintaining a standardized approach. This enhances readability and maintainability.

• Files with usage:
  • sectionUtils.ts
  • mainCanvasLayoutUtils.ts
  • index.ts
  • zoneUtils.ts

Ensure thorough testing to validate the functionality.

Scripts executed

The following scripts were executed for the analysis:

Script:

#!/bin/bash
# Description: Verify the integration of `addNewAnvilWidgetToDSL`.

# Test: Search for the function definition and its usage. Expect: Correct integration and usage.
rg --type ts -A 5 $'addNewAnvilWidgetToDSL'

Length of output: 7550

---

Line range hint 64-65:
Verify the integration of updateDraggedWidgets.

Ensure that the changes in updateDraggedWidgets are correctly reflected in addWidgetsToZone.

Verification successful

Let's verify the integration of updateDraggedWidgets within zoneUtils.ts to ensure that the changes are correctly reflected.

---

Verify the integration of updateDraggedWidgets.

The integration of the updateDraggedWidgets function within zoneUtils.ts appears to be correct. The function is used to update the updatedWidgets variable, which is then used to update zoneProps.children. This indicates that the changes in updateDraggedWidgets are correctly reflected in its usage.

• File: app/client/src/layoutSystems/anvil/utils/layouts/update/zoneUtils.ts
• Lines: 10-15

Review Outcome: No issues found with the integration.

Scripts executed

The following scripts were executed for the analysis:

Script:

#!/bin/bash
# Description: Verify the integration of `updateDraggedWidgets`.

# Test: Search for the function definition and its usage. Expect: Correct integration and usage.
rg --type ts -A 5 $'updateDraggedWidgets'

Length of output: 1248

---

Script:

#!/bin/bash
# Description: Extract full context of the `updateDraggedWidgets` call within `zoneUtils.ts`.

# Test: Display lines around the call to `updateDraggedWidgets` for detailed review.
rg --type ts -A 10 -B 10 'updateDraggedWidgets' app/client/src/layoutSystems/anvil/utils/layouts/update/zoneUtils.ts

Length of output: 1461

---

Line range hint 232-233:
Verify the integration of moveWidgetsToNewLayout.

Ensure that the changes in moveWidgetsToNewLayout are correctly reflected in moveWidgetsToZone.

Verification successful

---

Ensure the integration of moveWidgetsToNewLayout within moveWidgetsToZone

The integration appears to be correctly implemented. The function moveWidgetsToZone calls moveWidgetsToNewLayout when a large widget is present, ensuring the logic flows as intended.

• File: app/client/src/layoutSystems/anvil/utils/layouts/update/zoneUtils.ts
  • Function Definition:

    export function* moveWidgetsToZone(
      allWidgets: CanvasWidgetsReduxState,
      movedWidgets: string[],
      highlight: AnvilHighlightInfo,
    ) {
      const widgets: CanvasWidgetsReduxState = { ...allWidgets };
      const draggedWidgets: WidgetLayoutProps[] = transformMovedWidgets(
        widgets,
        movedWidgets,
        highlight,
      );
      const isLargeWidgetPresent = draggedWidgets.some((each) =>
        isLargeWidget(each.widgetType),
      );
      if (isLargeWidgetPresent) {
        const canvasWidgets: CanvasWidgetsReduxState = yield call(
          moveWidgetsToNewLayout,
          widgets,
          movedWidgets,
          highlight,
        );
        return canvasWidgets;
      } else {
        const updatedWidgets = moveWidgets(allWidgets, movedWidgets, highlight);
        return updatedWidgets;
      }
    }

This confirms that moveWidgetsToZone correctly integrates the updated moveWidgetsToNewLayout.

Scripts executed

The following scripts were executed for the analysis:

Script:

#!/bin/bash
# Description: Verify the integration of `moveWidgetsToNewLayout`.

# Test: Search for the function definition and its usage. Expect: Correct integration and usage.
rg --type ts -A 5 $'moveWidgetsToNewLayout'

Length of output: 1184

---

Script:

#!/bin/bash
# Description: Verify the integration of `moveWidgetsToNewLayout` in `moveWidgetsToZone`.

# Locate the definition of `moveWidgetsToZone` and its usage.
rg --type ts -A 10 $'function moveWidgetsToZone'

# Locate calls to `moveWidgetsToNewLayout` within `moveWidgetsToZone`.
rg --type ts -A 5 $'moveWidgetsToZone' | rg --type ts -A 5 $'moveWidgetsToNewLayout'

Length of output: 130

---

Script:

#!/bin/bash
# Description: Verify the integration of `moveWidgetsToNewLayout` in `moveWidgetsToZone`.

# Locate the definition of `moveWidgetsToZone`.
rg --type ts -A 10 'function moveWidgetsToZone'

# Locate calls to `moveWidgetsToNewLayout` within `moveWidgetsToZone`.
rg --type ts -A 10 'moveWidgetsToZone' | rg --type ts -A 10 'moveWidgetsToNewLayout'

Length of output: 132

---

Script:

#!/bin/bash
# Description: Verify the integration of `moveWidgetsToNewLayout` in `moveWidgetsToZone`.

# Locate the occurrences of `moveWidgetsToZone` and `moveWidgetsToNewLayout` with broader context.
rg --type ts -A 20 'moveWidgetsToZone'
rg --type ts -A 20 'moveWidgetsToNewLayout'

Length of output: 10841

---

Line range hint 194-195:
Verify the integration of addWidgetsToZone.

Ensure that the changes in addWidgetsToZone are correctly reflected in moveWidgetsToNewLayout.

app/client/src/layoutSystems/anvil/utils/layouts/update/sectionUtils.ts (4)

Line range hint 17-35:
Good use of the new function addNewAnvilWidgetToDSL.

The changes improve readability and maintainability by using an object format for parameters.

However, ensure that the new function is correctly integrated and tested.

Verification successful

---

Good use of the new function addNewAnvilWidgetToDSL.

The changes improve readability and maintainability by using an object format for parameters. The function appears to be correctly integrated across various parts of the codebase.

• sectionUtils.ts: Correctly uses addNewAnvilWidgetToDSL.
• zoneUtils.ts: Correctly uses addNewAnvilWidgetToDSL.
• mainCanvasLayoutUtils.ts: Correctly uses addNewAnvilWidgetToDSL.
• helpers.ts: Contains the function definition.

The integration seems to be thorough and consistent.

Scripts executed

The following scripts were executed for the analysis:

Script:

#!/bin/bash
# Description: Verify the integration of `addNewAnvilWidgetToDSL`.

# Test: Search for the function definition and its usage. Expect: Correct integration and usage.
rg --type ts -A 5 $'addNewAnvilWidgetToDSL'

Length of output: 7550

---

Line range hint 263-264:
Verify the integration of addWidgetsToSection.

Ensure that the changes in addWidgetsToSection are correctly reflected in moveWidgetsToSection.

Verification successful

Let's verify the integration of the addWidgetsToSection function within the moveWidgetsToSection function. We need to ensure that the changes in addWidgetsToSection are correctly reflected in its usage.

---

Let's broaden our search to ensure we capture the definition and usage of moveWidgetsToSection accurately.

---

Verify the integration of addWidgetsToSection within moveWidgetsToSection.

The moveWidgetsToSection function correctly integrates the addWidgetsToSection function. The changes in addWidgetsToSection are reflected in its usage within moveWidgetsToSection, ensuring proper functionality.

• Location of moveWidgetsToSection definition:

  • app/client/src/layoutSystems/anvil/utils/layouts/update/sectionUtils.ts

• Location of moveWidgetsToSection usage:

  • app/client/src/layoutSystems/anvil/integrations/sagas/anvilDraggingSagas/index.ts

Scripts executed

The following scripts were executed for the analysis:

Script:

#!/bin/bash
# Description: Verify the integration of `addWidgetsToSection`.

# Test: Search for the function definition and its usage. Expect: Correct integration and usage.
rg --type ts -A 5 $'addWidgetsToSection'

Length of output: 3338

---

Script:

#!/bin/bash
# Description: Verify the integration of `addWidgetsToSection` within `moveWidgetsToSection`.

# Search for the definition and usage of `moveWidgetsToSection`.
rg --type ts -A 10 $'function moveWidgetsToSection'

Length of output: 52

---

Script:

#!/bin/bash
# Description: Verify the integration of `addWidgetsToSection` within `moveWidgetsToSection`.

# Search for the definition and usage of `moveWidgetsToSection`.
rg --type ts -A 20 'moveWidgetsToSection'

Length of output: 6621

---

Line range hint 145-146:
Verify the integration of addZoneToSection.

Ensure that the changes in addZoneToSection are correctly reflected in addWidgetsToSection.

---

96-100: Good use of the new function addNewAnvilWidgetToDSL.

The changes improve readability and maintainability by using an object format for parameters.

However, ensure that the new function is correctly integrated and tested.

app/client/src/layoutSystems/anvil/integrations/sagas/anvilDraggingSagas/anvilDraggingSagas.test.ts (1)

2-2: Verify the new import of addWidgetsSaga.

Ensure that the new import is correctly integrated and tested.

Also applies to: 36-36

Verification successful

---

The new import of addWidgetsSaga is correctly integrated and tested.

• The addWidgetsSaga function is imported from ../anvilWidgetAdditionSagas.
• It is used appropriately within the test file anvilDraggingSagas.test.ts.
• The function is defined and utilized correctly within anvilWidgetAdditionSagas/index.ts.

Scripts executed

The following scripts were executed for the analysis:

Script:

#!/bin/bash
# Description: Verify the new import of `addWidgetsSaga`.

# Test: Search for the function definition and its usage. Expect: Correct integration and usage.
rg --type ts -A 5 $'addWidgetsSaga'

Length of output: 3965

app/client/src/layoutSystems/anvil/integrations/sagas/anvilWidgetAdditionSagas/index.ts (3)

163-208: LGTM!

The addWidgetsSaga function is well-structured and includes necessary error handling.

---

210-251: LGTM!

The addWidgetToGenericLayout function is well-structured and includes necessary operations.

---

253-261: LGTM!

The anvilWidgetAdditionSagas function is well-structured and correctly sets up the sagas.

app/client/src/layoutSystems/anvil/integrations/sagas/anvilWidgetAdditionSagas/helpers.ts (5)

69-83: LGTM!

The getUniqueWidgetName function is well-structured and includes necessary logic to ensure uniqueness.

---

93-114: LGTM!

The runBlueprintOperationsOnWidgets function is well-structured and includes necessary logic to handle blueprint operations.

Tools

Biome

[error] 105-105: Change to an optional chain.

Unsafe fix: Change to an optional chain.

(lint/complexity/useOptionalChain)

---

125-139: LGTM!

The addChildReferenceToParent function is well-structured and includes necessary logic to update the parent's children list.

---

149-201: LGTM!

The updateWidgetListWithNewWidget function is well-structured and includes necessary logic to handle widget addition.

---

212-248: LGTM!

The addNewAnvilWidgetToDSL function is well-structured and includes necessary logic to handle widget addition.

app/client/src/sagas/WidgetAdditionSagas.ts (5)

Line range hint 1-1:
Verify the impact of the removal of getWidgetSessionValues.

The removal of getWidgetSessionValues may impact the functionality of getChildWidgetProps. Ensure that the necessary properties are still being hydrated correctly.

---

Line range hint 1-1:
LGTM!

The generateChildWidgets function is well-structured and includes necessary logic to handle child widget generation.

---

Line range hint 1-1:
LGTM!

The getUpdateDslAfterCreatingChild function is well-structured and includes necessary logic to handle DSL updates.

---

Line range hint 1-1:
LGTM!

The addChildSaga function is well-structured and includes necessary error handling.

---

Line range hint 1-1:
LGTM!

The addNewTabChildSaga function is well-structured and includes necessary logic to handle tab child addition.

app/client/src/WidgetProvider/factory/index.tsx (3)

58-60: Good addition: widgetDefaultPropertiesMap

The introduction of widgetDefaultPropertiesMap is a smart move to manage default widget properties efficiently. By storing default properties for each widget type, it helps in reducing the number of properties passed during widget creation, thereby optimizing the DSL and preventing unnecessary clutter.

---

138-145: Clear and helpful comments

The comments explaining the purpose of widgetDefaultPropertiesMap are clear and provide valuable context. They effectively communicate the rationale behind using the map to optimize the widget addition process and reduce unnecessary properties in the DSL.

---

146-149: Good use of immutability with Object.freeze

The use of Object.freeze to set default properties in widgetDefaultPropertiesMap is commendable. It ensures that the default properties remain immutable, preventing any unintended modifications and maintaining the integrity of the widget configurations.

Files that changed from the base of the PR and between 5f4d092 and c690e28.

• app/client/src/layoutSystems/anvil/integrations/sagas/anvilWidgetAdditionSagas/index.ts (1 hunks)

• app/client/src/layoutSystems/anvil/integrations/sagas/anvilWidgetAdditionSagas/index.ts

Files that changed from the base of the PR and between c690e28 and 50d9f03.

• app/client/src/layoutSystems/anvil/integrations/sagas/anvilDraggingSagas/helpers.ts (1 hunks)
• app/client/src/layoutSystems/anvil/integrations/sagas/anvilWidgetAdditionSagas/helpers.test.ts (1 hunks)
• app/client/src/layoutSystems/anvil/integrations/sagas/anvilWidgetAdditionSagas/helpers.ts (1 hunks)
• app/client/src/layoutSystems/anvil/layoutComponents/presets/sectionPreset.tsx (1 hunks)
• app/client/src/layoutSystems/anvil/layoutComponents/presets/zonePreset.tsx (1 hunks)
• app/client/src/widgets/anvil/SectionWidget/widget/config/defaultConfig.ts (1 hunks)
• app/client/src/widgets/anvil/ZoneWidget/widget/config/defaultConfig.ts (3 hunks)

• app/client/src/layoutSystems/anvil/layoutComponents/presets/sectionPreset.tsx
• app/client/src/layoutSystems/anvil/layoutComponents/presets/zonePreset.tsx

• app/client/src/layoutSystems/anvil/integrations/sagas/anvilDraggingSagas/helpers.ts
• app/client/src/layoutSystems/anvil/integrations/sagas/anvilWidgetAdditionSagas/helpers.ts
• app/client/src/widgets/anvil/ZoneWidget/widget/config/defaultConfig.ts

app/client/src/widgets/anvil/SectionWidget/widget/config/defaultConfig.ts (1)

14-14: Verify the impact of property removals.

The properties boxShadow and detachFromLayout have been removed from the defaultConfig. Ensure that these properties are not required elsewhere in the codebase and that their removal does not affect the widget's functionality.

app/client/src/layoutSystems/anvil/integrations/sagas/anvilWidgetAdditionSagas/helpers.test.ts (4)

16-35: Test case for addChildReferenceToParent looks good!

The test case correctly verifies that a new child reference is added to the parent widget.

---

57-74: Test case for getUniqueWidgetName looks good!

The test case correctly verifies that a unique widget name is generated within the data tree.

---

77-116: Test case for runBlueprintOperationsOnWidgets looks good!

The test case correctly verifies that blueprint operations are executed on widgets as expected.

---

119-195: Test case for updateWidgetListWithNewWidget looks good!

The test case correctly verifies that the widget list is updated with a new widget as expected.