Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

feat: list building blocks in explorer #31199

Merged
merged 31 commits into from Mar 8, 2024

Conversation

jacquesikot
Copy link
Contributor

@jacquesikot jacquesikot commented Feb 19, 2024

Description

This is step 1 of completing the addition of building blocks within the canvas explorer. It adds building blocks to the explorer and hides the functionality behind a feature flag - release_drag_drop_building_blocks_enabled.

  1. Create a new hook to manage explorer items - widgets and building blocks
  2. Define the max items to display in the explorer for each tag
  3. Define a utility function to return all explorer items alongside the maxNoToRender per tag
  4. Rename WidgetSidebarWithTags to UIEntitySidebar and move into a new sidebar folder
  5. Adjust newly renamed UIEntitySidebar to implement loading for building blocks, new listing of blocks and widgets and manage "See more" functionality for all items in explorer.

PR fixes following issue(s)

Fixes #31146

Media

A video or a GIF is preferred. when using Loom, don’t embed because it looks like it’s a GIF. instead, just link to the video

Type of change

Please delete options that are not relevant.

  • Bug fix (non-breaking change which fixes an issue)
  • New feature (non-breaking change which adds functionality)
  • Breaking change (fix or feature that would cause existing functionality to not work as expected)
  • Chore (housekeeping or task changes that don't impact user perception)
  • This change requires a documentation update

Testing

How Has This Been Tested?

Please describe the tests that you ran to verify your changes. Also list any relevant details for your test configuration.
Delete anything that is not relevant

  • Manual
  • JUnit
  • Jest
  • Cypress

Test Plan

Add Testsmith test cases links that relate to this PR

Issues raised during DP testing

Link issues raised during DP testing for better visiblity and tracking (copy link from comments dropped on this PR)

Checklist:

Dev activity

  • My code follows the style guidelines of this project
  • I have performed a self-review of my own code
  • I have commented my code, particularly in hard-to-understand areas
  • I have made corresponding changes to the documentation
  • My changes generate no new warnings
  • I have added tests that prove my fix is effective or that my feature works
  • New and existing unit tests pass locally with my changes
  • PR is being merged under a feature flag

QA activity:

  • Speedbreak features have been covered
  • Test plan covers all impacted features and areas of interest
  • Test plan has been peer reviewed by project stakeholders and other QA members
  • Manually tested functionality on DP
  • We had an implementation alignment call with stakeholders post QA Round 2
  • Cypress test cases have been added and approved by SDET/manual QA
  • Added Test Plan Approved label after Cypress tests were reviewed
  • Added Test Plan Approved label after JUnit tests were reviewed

Summary by CodeRabbit

  • New Features

    • Introduced new constants and functions to optimize widget management and search functionality.
    • Added loading indicators and a "See More" button for better user interaction with widget cards.
    • Enhanced widget filtering and display based on user interactions and tag categories.
    • Implemented a custom hook for managing UI explorer items like widgets and building blocks.
  • Refactor

    • Updated import paths for better code organization and readability.
  • Style

    • Adjusted widget card rendering based on tags for an improved visual hierarchy and user experience.

@github-actions github-actions bot added Enhancement New feature or request Templates Issues related to templates Templates Pod Issues related to Templates labels Feb 19, 2024
Copy link
Contributor

coderabbitai bot commented Feb 19, 2024

Walkthrough

Walkthrough

The recent changes introduce the capability to list and manage building blocks within the platform's explorer, optimizing the widget search with Fuse.js, and enhancing user interaction through loading indicators and dynamic widget card rendering based on tags. It also lays the groundwork for drag-and-drop functionality of building blocks onto the canvas, streamlining the user experience for building applications. These updates collectively aim to accelerate user learning and improve the development process within the platform.

Changes

File Path Change Summary
.../constants/WidgetConstants.tsx Added BUILDING_BLOCKS constant, initialEntityCountForExplorerTag, and default size constants for building blocks in the explorer.
.../widgetSidebar/UIEntitySidebar.tsx Optimized widget search, managed widget card rendering, introduced loading indicators, and handled filtering/display based on tags.
.../widgetSidebar/WidgetCard.tsx Updated import path for useIsEditorPaneSegmentsEnabled.
.../Editor/utils.ts Added new constants and functions for widget deprecation messages, URL building, action responses, and widget card tagging.
.../widgetSidebar/UIEntityList.tsx Introduced UIEntityList component for rendering widget cards based on tags with a toggle for showing more items.
.../widgetSidebar/UIEntityTagGroup.tsx Added UIEntityTagGroup component for display and filtering of widget cards by tags, including search and loading state handling.
.../widgetSidebar/hooks.ts Introduced useUIExplorerItems hook for managing UI explorer items.
.../Editor/Explorer/index.tsx,
.../IDE/EditorPane/GlobalAdd.tsx,
.../IDE/EditorPane/UI/Add.tsx
Updated import paths for WidgetSidebarWithTags to UIEntitySidebar.
.../widgetSidebar/SeeMoreButton.tsx Added SeeMoreButton component for toggling content visibility.

Assessment against linked issues

Objective Addressed Explanation
Enhance user experience by enabling drag-and-drop functionality for building blocks on the canvas. (#31314) The PR sets foundational work for drag-and-drop but doesn't explicitly implement the functionality.
Implement a skeleton loader widget to indicate a loading state after a building block is dropped. (#31314) There's no mention of a skeleton loader widget specifically for post-drop visual feedback.
Streamline the process of integrating building blocks into the user's application. (#31314)
List all possible building blocks on the explorer as drag and drop items. (#31146)

Related issues

Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media?

Share

Tips

Chat

There are 3 ways to chat with CodeRabbit:

  • Review comments: Directly reply to a review comment made by CodeRabbit. Example:
    • I pushed a fix in commit <commit_id>.
    • Generate unit-tests for this file.
    • Open a follow-up GitHub issue for this discussion.
  • Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
    • @coderabbitai generate unit tests for this file.
    • @coderabbitai modularize this function.
  • PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
    • @coderabbitai generate interesting stats about this repository and render them as a table.
    • @coderabbitai show all the console.log statements in this repository.
    • @coderabbitai read src/utils.ts and generate unit tests.
    • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.

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 as PR comments)

  • @coderabbitai pause to pause the reviews on a PR.
  • @coderabbitai resume to resume the paused reviews.
  • @coderabbitai review to trigger a review. This is useful when automatic reviews are disabled for the repository.
  • @coderabbitai resolve resolve all the CodeRabbit review comments.
  • @coderabbitai help to get help.

Additionally, you can add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.

CodeRabbit Configration File (.coderabbit.yaml)

  • You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
  • The JSON schema for the configuration file is available here.
  • If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/coderabbit-overrides.v2.json

CodeRabbit Discord Community

Join our Discord Community to get help, request features, and share feedback.

Comment on lines 53 to 81
const BuildingBlockExplorerCard = (props: CardProps) => {
const type = `${props.details.type.split("_").join("").toLowerCase()}`;
const className = `t--widget-card-draggable t--widget-card-draggable-${type}`;

const onDragStart = (e: any) => {
e.preventDefault();
e.stopPropagation();
};
return (
<Wrapper
className={className}
data-guided-tour-id={`widget-card-${type}`}
draggable
id={`widget-card-draggable-${type}`}
onDragStart={onDragStart}
>
<div className="gap-2">
<StyledIconImg className="w-6 h-6" src={props.details.icon} />

<Text kind="body-s" style={{ fontWeight: 500 }}>
{props.details.displayName}
</Text>
{props.details.isBeta && <BetaLabel>Beta</BetaLabel>}
</div>
</Wrapper>
);
};

export default BuildingBlockExplorerCard;
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The BuildingBlockExplorerCard component's rendering logic is clear and concise. The use of destructuring for props.details and conditional rendering for the BetaLabel are best practices that enhance code readability and maintainability. However, the onDragStart handler prevents the default behavior and stops propagation, which might not be necessary unless specific drag-and-drop functionality is intended. If drag-and-drop is not a feature for these cards, consider removing the onDragStart handler to simplify the component.

- const onDragStart = (e: any) => {
-   e.preventDefault();
-   e.stopPropagation();
- };
- onDragStart={onDragStart}

Committable suggestion

‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation.

Suggested change
const BuildingBlockExplorerCard = (props: CardProps) => {
const type = `${props.details.type.split("_").join("").toLowerCase()}`;
const className = `t--widget-card-draggable t--widget-card-draggable-${type}`;
const onDragStart = (e: any) => {
e.preventDefault();
e.stopPropagation();
};
return (
<Wrapper
className={className}
data-guided-tour-id={`widget-card-${type}`}
draggable
id={`widget-card-draggable-${type}`}
onDragStart={onDragStart}
>
<div className="gap-2">
<StyledIconImg className="w-6 h-6" src={props.details.icon} />
<Text kind="body-s" style={{ fontWeight: 500 }}>
{props.details.displayName}
</Text>
{props.details.isBeta && <BetaLabel>Beta</BetaLabel>}
</div>
</Wrapper>
);
};
export default BuildingBlockExplorerCard;
const BuildingBlockExplorerCard = (props: CardProps) => {
const type = `${props.details.type.split("_").join("").toLowerCase()}`;
const className = `t--widget-card-draggable t--widget-card-draggable-${type}`;
return (
<Wrapper
className={className}
data-guided-tour-id={`widget-card-${type}`}
draggable
id={`widget-card-draggable-${type}`}
>
<div className="gap-2">
<StyledIconImg className="w-6 h-6" src={props.details.icon} />
<Text kind="body-s" style={{ fontWeight: 500 }}>
{props.details.displayName}
</Text>
{props.details.isBeta && <BetaLabel>Beta</BetaLabel>}
</div>
</Wrapper>
);
};
export default BuildingBlockExplorerCard;

@rahulbarwal
Copy link
Contributor

/build-deploy-preview

Copy link

Deploying Your Preview: https://github.com/appsmithorg/appsmith/actions/runs/7964808147.
Workflow: On demand build Docker image and deploy preview.
skip-tests: . env: .
PR: 31199.
recreate: .

Comment on lines 346 to 348
rows: 20,
columns: 5,
type: "BUILDING_BLOCK",
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

No numbers or strings in code, use constants file and then import it.
Can you briefly explain what rows and columns are doing here?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The preview box rows and columns when you drag a widget into the canvas, before it is dropped. I have added this to a constants file.

Comment on lines 70 to 77
const SEE_MORE_LESS_TEXT =
buildingBlockInitList === INITIAL_BUILDING_BLOCKS_IN_EXPLORER
? "See more"
: "See less";
const SEE_MORE_ARROW =
buildingBlockInitList === INITIAL_BUILDING_BLOCKS_IN_EXPLORER
? "arrow-down-s-line"
: "arrow-up-s-line";
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Nit: you can use useMemo here.

const buildingBlockCards = releaseDragDropBuildingBlocks
? transformTemplatesToWidgetCard(buildingBlocks)
: [];
const cards = [
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

useMemo here.

Comment on lines 51 to 55
const templatesCount = useSelector(templatesCountSelector);
const buildingBlocks = useSelector(getTemplatesSelector).filter(
(template) =>
template.functions[0] === TEMPLATE_BUILDING_BLOCKS_FILTER_FUNCTION_VALUE,
);
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Extracting bb, is a reusable logic... consider creating a custom hook for this(if possible).

If it does not make sense, lets extract it as a util atleast.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I have moved this logic to the selector

Comment on lines 238 to 261

{tag === WIDGET_TAGS.BUILDING_BLOCKS && (
<Button
className="mt-4"
data-testid="t--canvas-building-block-see-more"
kind="tertiary"
onClick={() => {
if (
buildingBlockInitList ===
INITIAL_BUILDING_BLOCKS_IN_EXPLORER
) {
setBuildingBlockInitList(buildingBlocks.length);
} else {
setBuildingBlockInitList(
INITIAL_BUILDING_BLOCKS_IN_EXPLORER,
);
}
}}
size="md"
startIcon={SEE_MORE_ARROW}
>
{SEE_MORE_LESS_TEXT}
</Button>
)}
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Can all this wrapper div with see more /less be extracted as a different component?

@rahulbarwal
Copy link
Contributor

@jacquesikot also see why Deepsource: JavaScript is failing for your PR.

Copy link

Deploy-Preview-URL: https://ce-31199.dp.appsmith.com

Copy link
Contributor

@sbalaji1192 sbalaji1192 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Can we connect over a call to discuss the WidgetSidebarWithTags.tsx changes?

app/client/src/ce/entities/FeatureFlag.ts Show resolved Hide resolved
app/client/src/pages/Editor/BuildingBlockExplorerCard.tsx Outdated Show resolved Hide resolved
app/client/src/pages/Editor/utils.ts Outdated Show resolved Hide resolved
app/client/src/pages/Editor/BuildingBlockExplorerCard.tsx Outdated Show resolved Hide resolved
app/client/src/pages/Editor/BuildingBlockExplorerCard.tsx Outdated Show resolved Hide resolved
app/client/src/pages/Editor/utils.ts Outdated Show resolved Hide resolved
app/client/src/pages/Editor/WidgetSidebarWithTags.tsx Outdated Show resolved Hide resolved
app/client/src/pages/Editor/WidgetSidebarWithTags.tsx Outdated Show resolved Hide resolved
@jacquesikot
Copy link
Contributor Author

/ok-to-test tags="@tag.Visual"

Copy link

github-actions bot commented Mar 7, 2024

Tests running at: https://github.com/appsmithorg/appsmith/actions/runs/8183521708.
Workflow: Appsmith External Integration Test Workflow.
Tags: @tag.Visual.

Copy link

github-actions bot commented Mar 7, 2024

Workflow run: https://github.com/appsmithorg/appsmith/actions/runs/8183521708.
Commit: ``.
Cypress dashboard url: Click here!
All cypress tests have passed 🎉🎉🎉

Copy link

github-actions bot commented Mar 7, 2024

Workflow run: https://github.com/appsmithorg/appsmith/actions/runs/8183515294.
Commit: ``.
Cypress dashboard url: Click here!
All cypress tests have passed 🎉🎉🎉

Copy link

github-actions bot commented Mar 7, 2024

Workflow run: https://github.com/appsmithorg/appsmith/actions/runs/8183509598.
Commit: ``.
Cypress dashboard: Click here!
The following are new failures, please fix them before merging the PR:

  1. cypress/e2e/Regression/ClientSide/Templates/BuildingBlocks/StarterBuildingBlocksOnCanvas_spec.ts

To know the list of identified flaky tests - Refer here

Copy link

github-actions bot commented Mar 7, 2024

Workflow run: https://github.com/appsmithorg/appsmith/actions/runs/8183509598.
Commit: ``.
Cypress dashboard: Click here!
The following are new failures, please fix them before merging the PR:

  1. cypress/e2e/Regression/ClientSide/Templates/BuildingBlocks/StarterBuildingBlocksOnCanvas_spec.ts

To know the list of identified flaky tests - Refer here

@jacquesikot
Copy link
Contributor Author

/ok-to-test tags="@tag.Templates"

Copy link

github-actions bot commented Mar 7, 2024

Tests running at: https://github.com/appsmithorg/appsmith/actions/runs/8185957561.
Workflow: Appsmith External Integration Test Workflow.
Tags: @tag.Templates.

Copy link

github-actions bot commented Mar 7, 2024

Workflow run: https://github.com/appsmithorg/appsmith/actions/runs/8185957561.
Commit: ``.
Cypress dashboard url: Click here!
All cypress tests have passed 🎉🎉🎉

@jacquesikot
Copy link
Contributor Author

/ok-to-test tags="@tag.Templates"

Copy link

github-actions bot commented Mar 7, 2024

Tests running at: https://github.com/appsmithorg/appsmith/actions/runs/8186836795.
Workflow: Appsmith External Integration Test Workflow.
Tags: @tag.Templates.

Copy link

github-actions bot commented Mar 7, 2024

Workflow run: https://github.com/appsmithorg/appsmith/actions/runs/8186836795.
Commit: ``.
Cypress dashboard: Click here!
The following are new failures, please fix them before merging the PR:

  1. cypress/e2e/Regression/ClientSide/Templates/BuildingBlocks/StarterBuildingBlocksOnCanvas_spec.ts

  2. cypress/e2e/Regression/ClientSide/Templates/CreateNewAppFromTemplates_spec.ts
  3. cypress/e2e/Regression/ClientSide/Templates/Filtering/TemplatesModal_filtering_spec.ts
  4. cypress/e2e/Regression/ClientSide/Templates/Fork_Template_Existing_app_spec.js
  5. cypress/e2e/Regression/ClientSide/Templates/Fork_Template_To_App_spec.ts
  6. cypress/e2e/Regression/ClientSide/Templates/Fork_Template_spec.js
  7. cypress/e2e/Regression/ClientSide/Templates/TemplatesPage_spec.ts
To know the list of identified flaky tests - Refer here

@rahulbarwal
Copy link
Contributor

/ok-to-test tags="@tag.Templates"

Copy link

github-actions bot commented Mar 7, 2024

Tests running at: https://github.com/appsmithorg/appsmith/actions/runs/8188399354.
Workflow: Appsmith External Integration Test Workflow.
Tags: @tag.Templates.

Copy link

github-actions bot commented Mar 7, 2024

Workflow run: https://github.com/appsmithorg/appsmith/actions/runs/8188399354.
Commit: ``.
Cypress dashboard: Click here!
The following are new failures, please fix them before merging the PR:

  1. cypress/e2e/Regression/ClientSide/Templates/BuildingBlocks/StarterBuildingBlocksOnCanvas_spec.ts

  2. cypress/e2e/Regression/ClientSide/Templates/CreateNewAppFromTemplates_spec.ts
  3. cypress/e2e/Regression/ClientSide/Templates/Filtering/TemplatesModal_filtering_spec.ts
  4. cypress/e2e/Regression/ClientSide/Templates/Fork_Template_Existing_app_spec.js
  5. cypress/e2e/Regression/ClientSide/Templates/Fork_Template_To_App_spec.ts
  6. cypress/e2e/Regression/ClientSide/Templates/Fork_Template_spec.js
  7. cypress/e2e/Regression/ClientSide/Templates/TemplatesPage_spec.ts
To know the list of identified flaky tests - Refer here

@rahulbarwal
Copy link
Contributor

/ok-to-test tags="@tag.Templates"

Copy link

github-actions bot commented Mar 7, 2024

Tests running at: https://github.com/appsmithorg/appsmith/actions/runs/8190589402.
Workflow: Appsmith External Integration Test Workflow.
Tags: @tag.Templates.

Copy link

github-actions bot commented Mar 7, 2024

Workflow run: https://github.com/appsmithorg/appsmith/actions/runs/8190589402.
Commit: ``.
Cypress dashboard: Click here!
The following are new failures, please fix them before merging the PR:

  1. cypress/e2e/Regression/ClientSide/Templates/BuildingBlocks/StarterBuildingBlocksOnCanvas_spec.ts

  2. cypress/e2e/Regression/ClientSide/Templates/CreateNewAppFromTemplates_spec.ts
  3. cypress/e2e/Regression/ClientSide/Templates/Filtering/TemplatesModal_filtering_spec.ts
  4. cypress/e2e/Regression/ClientSide/Templates/Fork_Template_Existing_app_spec.js
  5. cypress/e2e/Regression/ClientSide/Templates/Fork_Template_To_App_spec.ts
  6. cypress/e2e/Regression/ClientSide/Templates/Fork_Template_spec.js
  7. cypress/e2e/Regression/ClientSide/Templates/TemplatesPage_spec.ts
To know the list of identified flaky tests - Refer here

@rahulbarwal
Copy link
Contributor

/ok-to-test tags="@tag.Templates"

Copy link

github-actions bot commented Mar 8, 2024

Tests running at: https://github.com/appsmithorg/appsmith/actions/runs/8198757793.
Workflow: Appsmith External Integration Test Workflow.
Tags: @tag.Templates.

Copy link

github-actions bot commented Mar 8, 2024

Workflow run: https://github.com/appsmithorg/appsmith/actions/runs/8198757793.
Commit: ``.
Cypress dashboard url: Click here!
All cypress tests have passed 🎉🎉🎉

@jacquesikot jacquesikot merged commit 0cf0901 into release Mar 8, 2024
15 checks passed
@jacquesikot jacquesikot deleted the feat/list-building-blocks-in-explorer branch March 8, 2024 09:05
rahulbarwal pushed a commit that referenced this pull request Mar 8, 2024
…1406)

## Description
**Goal**
To allow users drag and drop building blocks on the canvas just like
widgets today. We are also implementing a loading state with the
platform skeleton component immediately the user drops the block on the
canvas.

**Why**
The dropping of building blocks needs to make an API call to the backend
to process adding the building block functionality to the users app.
This loading skeleton acts as a placeholder for the block while the API
call is processing.

**How**
1. We had listed the building blocks in a previous
[PR](#31199)
2. Created a new saga to handle widget and building block addition
called `addUIEntitySaga`
3. The saga handles widget addition like it did previously, but also
handles building block addition to canvas.

#### PR fixes following issue(s)
Fixes #31314 

#### Media

#### Type of change
> Please delete options that are not relevant.
- New feature (non-breaking change which adds functionality)

## Testing
>
#### How Has This Been Tested?
> Please describe the tests that you ran to verify your changes. Also
list any relevant details for your test configuration.
> Delete anything that is not relevant
- [ ] Manual
- [ ] JUnit
- [ ] Jest
- [ ] Cypress
>
>
#### Test Plan
> Add Testsmith test cases links that relate to this PR
>
>
#### Issues raised during DP testing
> Link issues raised during DP testing for better visiblity and tracking
(copy link from comments dropped on this PR)
>
>
>
## Checklist:
#### Dev activity
- [ ] My code follows the style guidelines of this project
- [ ] I have performed a self-review of my own code
- [ ] I have commented my code, particularly in hard-to-understand areas
- [ ] I have made corresponding changes to the documentation
- [ ] My changes generate no new warnings
- [ ] I have added tests that prove my fix is effective or that my
feature works
- [ ] New and existing unit tests pass locally with my changes
- [ ] PR is being merged under a feature flag


#### QA activity:
- [ ] [Speedbreak
features](https://github.com/appsmithorg/TestSmith/wiki/Guidelines-for-test-plans#speedbreakers-)
have been covered
- [ ] Test plan covers all impacted features and [areas of
interest](https://github.com/appsmithorg/TestSmith/wiki/Guidelines-for-test-plans#areas-of-interest-)
- [ ] Test plan has been peer reviewed by project stakeholders and other
QA members
- [ ] Manually tested functionality on DP
- [ ] We had an implementation alignment call with stakeholders post QA
Round 2
- [ ] Cypress test cases have been added and approved by SDET/manual QA
- [ ] Added `Test Plan Approved` label after Cypress tests were reviewed
- [ ] Added `Test Plan Approved` label after JUnit tests were reviewed


<!-- This is an auto-generated comment: release notes by coderabbit.ai
-->
## Summary by CodeRabbit

- **New Features**
- Introduced drag-and-drop functionality for building blocks within the
canvas editor.
- Added a new feature flag to enable/disable drag-and-drop building
blocks.
- Implemented new UI components such as `SeeMoreButton`, `UIEntityList`,
and `UIEntitySidebar` for enhanced widget management and exploration.
- Enhanced widget sidebar with improved search and filter capabilities.

- **Enhancements**
- Updated various components and sagas to support the new drag-and-drop
functionality and building blocks management.
- Improved loading and organization of UI explorer items, including
widgets and building blocks.

- **Refactor**
- Adjusted import paths and reorganized imports across multiple files
for better code maintenance.
- Consolidated widget addition logic under a unified saga for handling
different UI entity types.

- **Bug Fixes**
- Fixed the directory structure for the `useIsEditorPaneSegmentsEnabled`
hook to reflect recent changes.
<!-- end of auto-generated comment: release notes by coderabbit.ai -->
@coderabbitai coderabbitai bot mentioned this pull request Apr 29, 2024
2 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Enhancement New feature or request Templates Pod Issues related to Templates Templates Issues related to templates
Projects
None yet
Development

Successfully merging this pull request may close these issues.

[Feature]: List building blocks on explorer
3 participants