-
Notifications
You must be signed in to change notification settings - Fork 4.7k
chore: move wds widgets to modules #36511
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
Changes from all commits
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -1,4 +1,4 @@ | ||
| import type { Validation } from "widgets/wds/WDSInputWidget/widget/types"; | ||
| import type { Validation } from "modules/ui-builder/ui/wds/WDSInputWidget/widget/types"; | ||
|
Contributor
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. 💡 Codebase verification Attention, class! It appears that the Please ensure that the Analysis chainClass, let's examine this import statement change! Good job updating the import path! This change aligns well with our lesson plan of moving WDS widgets to modules. It's like organizing your school supplies into different folders - it makes everything easier to find! However, we need to make sure this new path is correct. Can you double-check that the Let's run a quick test to make sure everything is in order: Remember, always double-check your work! Alright class, it looks like our previous search didn't turn up the Scripts executedThe following scripts were executed for the analysis: Script: #!/bin/bash
# Description: Verify the existence of the Validation type in the new location
# Test: Search for the Validation type definition in the new path
ast-grep --lang typescript --pattern 'export type Validation = $_' -- modules/ui-builder/ui/wds/WDSInputWidget/widget/types.ts
# If the above command doesn't find anything, let's check if the file exists
if [ $? -ne 0 ]; then
echo "Validation type not found. Checking if the file exists:"
fd --type file "types.ts" modules/ui-builder/ui/wds/WDSInputWidget/widget
fi
Length of output: 250 Script: #!/bin/bash
# Description: Search for all types.ts files within WDSInputWidget directory
fd --type file "types.ts" modules/ui-builder/ui/wds/WDSInputWidget/widget
#!/bin/bash
# Description: Search for the Validation type definition across the codebase
ast-grep --lang typescript --pattern 'export type Validation = $_' --
Length of output: 280 Script: #!/bin/bash
# Description: Find all types.ts files in the codebase
fd --type file "types.ts"
#!/bin/bash
# Description: Search for the Validation type definition across the entire codebase
ast-grep --lang typescript --pattern 'export type Validation = $_' --
Length of output: 10228 |
||
|
|
||
| import type { CheckboxGroupWidgetProps } from "./types"; | ||
|
|
||
|
|
||
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -1,5 +1,5 @@ | ||
| import { WIDGET_TAGS } from "constants/WidgetConstants"; | ||
| import { WDSInputWidget } from "widgets/wds/WDSInputWidget"; | ||
| import { WDSInputWidget } from "modules/ui-builder/ui/wds/WDSInputWidget"; | ||
|
Contributor
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. 💡 Codebase verification Great progress on updating the import paths! However, it appears that To ensure our application runs smoothly, please verify that Analysis chainClass, let's examine this import statement change. Good job on updating the import path for Let's do a quick pop quiz to verify this change: Remember, class, it's important to double-check our work! Great effort so far! It looks like we encountered a few hiccups with our initial verification scripts. Let's refine our approach to ensure everything is in order. Please run the above scripts to gather more accurate information. This will help us confirm that the import path has been updated correctly and that no lingering references to the old path remain. Keep up the excellent work, and let's ensure our codebase remains clean and well-organized! Excellent persistence! Let's delve deeper to ensure everything is in perfect order. Please execute the above scripts to further verify the presence and correct usage of Hmm, it seems like Please run the above scripts to locate Scripts executedThe following scripts were executed for the analysis: Script: #!/bin/bash
# Description: Verify the existence of the new WDSInputWidget path and its usage
# Test 1: Check if the new file exists
echo "Test 1: Checking if the new file exists"
fd --type f "WDSInputWidget" modules/ui-builder/ui/wds
# Test 2: Check for any remaining references to the old path
echo "Test 2: Checking for any remaining references to the old path"
rg --type typescript "from\s+['\"]widgets/wds/WDSInputWidget"
# Test 3: Check for usage of the new path
echo "Test 3: Checking for usage of the new path"
rg --type typescript "from\s+['\"]modules/ui-builder/ui/wds/WDSInputWidget"
Length of output: 700 Script: #!/bin/bash
# Description: Enhanced verification of WDSInputWidget import path and usage
# Test 1: Locate all instances of WDSInputWidget in the codebase
echo "Test 1: Searching for all WDSInputWidget files in the repository"
fd "WDSInputWidget" --type f
# Test 2: Check for any remaining references to the old import path
echo "Test 2: Checking for remaining references to the old import path"
rg --glob '*.ts' "from\s+['\"]widgets/wds/WDSInputWidget['\"]"
# Test 3: Verify usage of the new import path across the codebase
echo "Test 3: Verifying usage of the new import path"
rg --glob '*.ts' "from\s+['\"]modules/ui-builder/ui/wds/WDSInputWidget['\"]"
Length of output: 668 Script: #!/bin/bash
# Description: Comprehensive search for WDSInputWidget files and their exports
# Test 1: Locate all instances of WDSInputWidget in the repository
echo "Test 1: Searching for all WDSInputWidget files in the repository"
fd "WDSInputWidget" --type f
# Test 2: Verify that WDSInputWidget is exported properly in its module
echo "Test 2: Checking exports of WDSInputWidget"
ast-grep --lang typescript --pattern $'export\s+class WDSInputWidget { $$$ }'
# Test 3: Ensure all imports of WDSInputWidget are updated to the new path
echo "Test 3: Verifying all imports of WDSInputWidget use the new path"
rg --glob '*.ts' "from\s+['\"]modules/ui-builder/ui/wds/WDSInputWidget['\"]"
Length of output: 670 Script: #!/bin/bash
# Description: Comprehensive search for WDSInputWidget files and their exports
# Test 1: Find all files related to WDSInputWidget in the repository
echo "Test 1: Searching for all WDSInputWidget files in the repository"
fd "WDSInputWidget"
# Test 2: Check if WDSInputWidget is exported properly in any module
echo "Test 2: Checking exports of WDSInputWidget"
ast-grep --lang typescript --pattern $'export\s+class WDSInputWidget { $$$ }'
# Test 3: Verify all imports of WDSInputWidget use the correct new path
echo "Test 3: Verifying all imports of WDSInputWidget use the new path"
rg --glob '*.ts*' "from\s+['\"]modules/ui-builder/ui/wds/WDSInputWidget['\"]"
Length of output: 1490 |
||
| import { KeyValueIcon, KeyValueThumbnail } from "appsmith-icons"; | ||
| import type { WidgetBaseConfiguration } from "WidgetProvider/constants"; | ||
|
|
||
|
|
||
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
💡 Codebase verification
❌ Import Paths Verification Failed
It appears that the new import paths for the WDS widgets are pointing to files that do not exist in the specified directory. Please verify the following:
File Locations:
WDSSectionWidget.tsis present inmodules/ui-builder/ui/wds/.WDSZoneWidget.tsis present inmodules/ui-builder/ui/wds/.WDSButtonWidget.tsis present inmodules/ui-builder/ui/wds/.Import Paths:
Addressing these points will help prevent potential compilation errors and ensure that the tests run smoothly.
Analysis chain
Very good job updating the import statements, class!
I see you've diligently updated the import paths for our WDS widgets. This aligns perfectly with our lesson plan of moving these widgets to modules. Well done!
However, as a responsible student, I want you to double-check that these new imports are working correctly. Can you please run the tests to ensure everything is still functioning as expected?
Let's verify these imports by running the following command:
Also applies to: 23-23
Excellent progress on updating the import statements!
Since the
tsccommand isn't available in our environment, let's ensure that the new import paths correctly point to existing files. Please run the following commands to verify that each imported WDS widget exists in the specified directories:Scripts executed
The following scripts were executed for the analysis:
Script:
Length of output: 185
Script:
Length of output: 794