de443104f2
4 Commits
| Author | SHA1 | Message | Date | |
|---|---|---|---|---|
Jacques Ikot
|
2fbc831109
|
fix: add implementation for onForkButtonTrigger in building block (#29976)
## Description **Issue** On the templates tab, when clicking the fork button on the building block card, it navigates to the building block detail screen, this is not the intended action. Navigating to the details screen should happen only when the card component itself is clicked. If the fork button is clicked directly, the fork application init modal should show up. **Changes Made** To address this issue, I've updated the onForkButtonTrigger function within the building block component. I've introduced the forkTemplateDialog modal and integrated it into the function. Now, when users click on the fork button, the modal is triggered for the normal fork template flow like in the rest of the templates. **House Cleaning** In the process of addressing the main issue, I took the opportunity to enhance code clarity. Specifically, I identified and improved comments in the test storage utility. The utility previously contained a switch statement that returned different store states, but lacked clear descriptions on how to effectively utilize the returned stores. With the updated comments, developers can now easily understand and leverage the various store states returned by the switch statement, contributing to a more comprehensible codebase. #### PR fixes following issue(s) Issue - #29982 #### Type of change > Please delete options that are not relevant. - Bug fix (non-breaking change which fixes an issue) - Chore (housekeeping or task changes that don't impact user perception) ## 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 #### Issues raised during DP testing ## 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** - Enhanced onboarding process with step-specific scenarios for a personalized experience. - Introduced a modal for forking templates to streamline user interactions. - **Improvements** - Implemented state management in the template building block for better user interface responsiveness. - **Documentation** - Added descriptive alt text constants for building block thumbnails for improved accessibility. <!-- end of auto-generated comment: release notes by coderabbit.ai --> |
||
|
Jacques Ikot
|
c8217e63a5
|
feat: improve templates listing page in start with templates flow (#29524)
## Description Enhancements to Templates Gallery: 1. Fixed Template Heights: Adjusted the template card display to feature a fixed height for each template, providing a consistent and visually appealing layout. 2. Title Update to "Operations": Revised the section title from "Templates" to "Operations" to better reflect the purpose and content of the gallery. 3. New Card for Building Blocks: Created a new card to accommodate building blocks seamlessly. This enhancement ensures a more comprehensive representation of the available elements within each template. 4. Transition to Grid Layout: Replaced the Masonry layout with a grid structure for improved alignment and visual harmony between templates and building blocks. This change enhances the overall organization and presentation of content within the gallery. Figma - https://www.figma.com/file/kbU9xPv44neCfv1FFo9Ndu/User-Activation?type=design&node-id=4293-41441&mode=design&t=nPvqyNdtbtsKmvm2-0 #### PR fixes following issue(s) Fixes #29456 #### Media #### Type of change - 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 styled components for improved layout and design of building block templates. - Added a new "Fork" button with tooltip functionality to Building Block components. - Implemented a grid layout for template presentation using the new `TemplateGrid` styled component. - Created a `FixedHeightTemplate` component to enforce consistent sizing and text truncation for template elements. - **Enhancements** - Updated the `BuildingBlock` component to support a new `onForkTemplateClick` event. - Refined the visual presentation and layout of templates with updated CSS styles. - Improved the template filtering interface with new selectors and loading indicators. - Enhanced the `TemplatesContent` component to include search functionality and display the count of templates and filters. - **Bug Fixes** - Fixed issues with template rendering by replacing the use of `Masonry` with `TemplateGrid`. - Adjusted the `RequestTemplate` component to correctly display the request text based on the `isBuildingBlock` prop. - **Refactor** - Refactored the `TemplatesContent` component into `StartWithTemplateContent` and `StartWithTemplateFilters` for better modularity. - Removed redundant code and imports across various template-related components and files. - Streamlined test scripts by introducing custom helper functions for template interactions. - **Documentation** - Added a new message constant `REQUEST_BUILDING_BLOCK` for requesting building blocks. - **Style** - Applied updated styles to the `SearchWrapper` and `ModalContentWrapper` components for better visual consistency. - **Chores** - Updated the `TEMPLATE_BUILDING_BLOCKS_FILTER_FUNCTION_VALUE` constant to reflect the correct terminology. - **Tests** - Modified test cases related to filtering templates and forking templates to reflect changes in the UI and functionality. <!-- end of auto-generated comment: release notes by coderabbit.ai --> --------- Co-authored-by: Rahul Barwal <rahul.barwal@appsmith.com> |
||
|
Jacques Ikot
|
be308fab43
|
feat: update template screen UI and building blocks for new users in start from use case flow (#29020)
> Pull Request Template > > Use this template to quickly create a well written pull request. Delete all quotes before creating the pull request. > ## Description Updating the UI for the start from use case flow for new users + adding building blocks to the list of templates offered to new users in this flow. > > Please include a summary of the changes and which issue has been fixed. Please also include relevant motivation > and context. List any dependencies that are required for this change > > Links to Notion, Figma or any other documents that might be relevant to the PR > https://www.figma.com/file/kbU9xPv44neCfv1FFo9Ndu/User-Activation?node-id=4293:41450&mode=dev > https://www.notion.so/appsmith/Activation-experiment-2-Start-from-a-template-Offer-building-blocks-in-addition-to-templates-8986dfc3629041559c81b1650b3a5fe5?pvs=4 #### PR fixes following issue(s) Fixes #28605 > if no issue exists, please create an issue and ask the maintainers about this first > > #### 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 - [x] 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 - [x] My code follows the style guidelines of this project - [x] I have performed a self-review of my own code - [x] I have commented my code, particularly in hard-to-understand areas - [ ] I have made corresponding changes to the documentation - [x] 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 - [x] 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 |
||
|
akash-codemonk
|
65aee7fd14
|
feat: Application templates (#10964) |