Remove changes to Webflow pre-migration #14827
Conversation
|
The latest updates on your projects. Learn more about Vercel for Git ↗︎ |
WalkthroughThe changes in this pull request involve significant updates to the Webflow integration components. The Changes
Suggested labels
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? 🪧 TipsChatThere are 3 ways to chat with CodeRabbit:
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
CodeRabbit Configuration File (
|
malexanderlim
deleted the
revert-14826-revert-14824-revert-14818-webflow-migration-followup
branch
![coderabbitai[bot]](https://avatars.githubusercontent.com/in/347564?s=60&v=4){kind=small}
There was a problem hiding this comment.
Actionable comments posted: 10
🧹 Outside diff range and nitpick comments (6)
components/webflow_v2/sources/changed-collection-item/changed-collection-item.mjs (1)
7-7: Consider maintaining webhook-specific documentation linkThe documentation link has been changed from a webhook-specific reference to a general API reference. While this aligns with the revert operation, consider maintaining webhook-specific documentation for better developer experience in future updates.
components/webflow_v2/sources/changed-ecommerce-order/changed-ecommerce-order.mjs (1)
7-7: Documentation URL change impacts developer experienceThe documentation link has changed from the webhooks reference to the order model section. This might affect developers looking for webhook-specific information.
Consider maintaining both links or using the more specific webhooks documentation for this webhook-related component.
components/webflow_v2/actions/update-item-inventory/update-item-inventory.mjs (1)
Line range hint
49-52: Remove unnecessary eslint-disable commentThe
siteIdparameter is used in thepropDefinitionforcollections, so the eslint-disable comment appears unnecessary.const { app, - // eslint-disable-next-line no-unused-vars siteId, collectionId, itemId, ...data } = this;components/webflow_v2/actions/list-sites/list-sites.mjs (1)
Line range hint
12-18: Consider enhancing the success message with site countThe current success message is generic. Consider making it more informative by including the number of sites retrieved.
- $.export("$summary", "Successfully retrieved sites"); + $.export("$summary", `Successfully retrieved ${response.length} sites`);components/webflow_v2/actions/get-item-inventory/get-item-inventory.mjs (1)
Line range hint
1-41: Reconsider the versioning strategyThe changes suggest introducing a v2 version of the Webflow integration while the PR intends to revert changes. This mixed approach could lead to:
- Confusion about which version to use
- Maintenance overhead of managing multiple versions
- Potential breaking changes for existing users
Consider either:
- Fully reverting to the original implementation, or
- Creating a clear migration path if v2 is intended
components/webflow_v2/actions/create-collection-item/create-collection-item.mjs (1)
Line range hint
1-70: Consider updating field type documentation linkWhile reverting the main API documentation link, the field types documentation link in the
additionalPropsmethod still points to the newer API documentation:
https://developers.webflow.com/reference/field-types-item-valuesConsider updating this link to maintain consistency with the older API documentation being used.
📜 Review details
Configuration used: CodeRabbit UI
Review profile: CHILL
⛔ Files ignored due to path filters (1)
pnpm-lock.yamlis excluded by!**/pnpm-lock.yaml
📒 Files selected for processing (31)
components/webflow/package.json(2 hunks)components/webflow/webflow.app.mjs(2 hunks)components/webflow_v2/actions/create-collection-item/create-collection-item.mjs(1 hunks)components/webflow_v2/actions/delete-collection-item/delete-collection-item.mjs(1 hunks)components/webflow_v2/actions/fulfill-order/fulfill-order.mjs(1 hunks)components/webflow_v2/actions/get-collection-item/get-collection-item.mjs(1 hunks)components/webflow_v2/actions/get-collection/get-collection.mjs(1 hunks)components/webflow_v2/actions/get-item-inventory/get-item-inventory.mjs(1 hunks)components/webflow_v2/actions/get-order/get-order.mjs(1 hunks)components/webflow_v2/actions/get-site/get-site.mjs(1 hunks)components/webflow_v2/actions/list-collection-items/list-collection-items.mjs(1 hunks)components/webflow_v2/actions/list-collections/list-collections.mjs(1 hunks)components/webflow_v2/actions/list-orders/list-orders.mjs(1 hunks)components/webflow_v2/actions/list-sites/list-sites.mjs(1 hunks)components/webflow_v2/actions/publish-site/publish-site.mjs(1 hunks)components/webflow_v2/actions/refund-order/refund-order.mjs(1 hunks)components/webflow_v2/actions/unfulfill-order/unfulfill-order.mjs(1 hunks)components/webflow_v2/actions/update-collection-item/update-collection-item.mjs(1 hunks)components/webflow_v2/actions/update-item-inventory/update-item-inventory.mjs(1 hunks)components/webflow_v2/actions/update-order/update-order.mjs(1 hunks)components/webflow_v2/package.json(1 hunks)components/webflow_v2/sources/changed-collection-item/changed-collection-item.mjs(1 hunks)components/webflow_v2/sources/changed-ecommerce-inventory/changed-ecommerce-inventory.mjs(1 hunks)components/webflow_v2/sources/changed-ecommerce-order/changed-ecommerce-order.mjs(1 hunks)components/webflow_v2/sources/common/common.mjs(1 hunks)components/webflow_v2/sources/new-collection-item/new-collection-item.mjs(1 hunks)components/webflow_v2/sources/new-deleted-collection-item/new-deleted-collection-item.mjs(1 hunks)components/webflow_v2/sources/new-ecommerce-order/new-ecommerce-order.mjs(1 hunks)components/webflow_v2/sources/new-form-submission/new-form-submission.mjs(1 hunks)components/webflow_v2/sources/new-site-published/new-site-published.mjs(1 hunks)components/webflow_v2/webflow_v2.app.mjs(1 hunks)
✅ Files skipped from review due to trivial changes (2)
- components/webflow_v2/sources/common/common.mjs
- components/webflow_v2/package.json
🧰 Additional context used
🪛 GitHub Check: Lint Code Base
components/webflow_v2/sources/new-site-published/new-site-published.mjs
[warning] 6-6:
Source names should start with "New". See https://pipedream.com/docs/components/guidelines/#source-name
components/webflow_v2/sources/changed-collection-item/changed-collection-item.mjs
[warning] 6-6:
Source names should start with "New". See https://pipedream.com/docs/components/guidelines/#source-name
components/webflow_v2/sources/new-deleted-collection-item/new-deleted-collection-item.mjs
[warning] 6-6:
Source names should start with "New". See https://pipedream.com/docs/components/guidelines/#source-name
components/webflow_v2/sources/changed-ecommerce-inventory/changed-ecommerce-inventory.mjs
[warning] 6-6:
Source names should start with "New". See https://pipedream.com/docs/components/guidelines/#source-name
components/webflow_v2/sources/changed-ecommerce-order/changed-ecommerce-order.mjs
[warning] 6-6:
Source names should start with "New". See https://pipedream.com/docs/components/guidelines/#source-name
🔇 Additional comments (56)
components/webflow_v2/sources/changed-collection-item/changed-collection-item.mjs (1)
5-5: LGTM: Component key change
The key change to include webflow_v2 prefix is consistent with the component restructuring and helps prevent conflicts with the original webflow component.
components/webflow_v2/actions/refund-order/refund-order.mjs (3)
Line range hint 10-31: LGTM: Props and implementation unchanged
The core functionality remains intact:
- Props configuration maintains the required site and order ID inputs
- The refund implementation logic is unchanged
- Error handling and response handling remain consistent
4-4: Review component metadata changes
The changes align with the revert objectives:
- Key updated to include v2 prefix
- Documentation link updated to match pre-migration state
- Version reset to 0.0.1 is appropriate for a fresh start
However, let's verify the documentation URL is still valid and accessible.
Also applies to: 6-7
✅ Verification successful
Documentation URLs are consistent across Webflow v2 components
The verification shows that all Webflow v2 components consistently use the same documentation URL format (developers.webflow.com/#), and there are no instances of the old format (developers.webflow.com/data/reference). This confirms that the documentation link changes in the refund-order component align with the rest of the v2 components.
🏁 Scripts executed
The following scripts were executed for the analysis:
Script:
#!/bin/bash
# Description: Check if similar documentation URLs are used consistently across the codebase
# Search for other Webflow v2 documentation links to ensure consistency
rg -l "developers\.webflow\.com/#" "components/webflow_v2"
# Check for any mixed usage of old and new doc formats
rg -l "developers\.webflow\.com/data/reference" "components/webflow_v2"
Length of output: 1970
1-1: Verify the import path exists
Since this is a revert PR, let's verify that the webflow_v2.app.mjs module exists and is properly placed.
✅ Verification successful
Import path is correctly configured
The verification confirms that webflow_v2.app.mjs exists at the expected location components/webflow_v2/webflow_v2.app.mjs and there are no conflicting app files in the directory.
🏁 Scripts executed
The following scripts were executed for the analysis:
Script:
#!/bin/bash
# Description: Verify the existence and location of webflow_v2.app.mjs
# Check if the file exists
fd -p "components/webflow_v2/webflow_v2.app.mjs$"
# Check for any potential duplicate or conflicting app files
fd -p "components/webflow_v2/.*app.mjs$"
Length of output: 176
components/webflow_v2/sources/changed-ecommerce-order/changed-ecommerce-order.mjs (1)
8-8: Version downgrade requires attention
The version downgrade from "1.0.0" to "0.0.1" is significant and might affect:
- Semantic versioning expectations
- Dependency management
- Upgrade paths for existing users
Please verify if this aggressive version downgrade is intentional and necessary.
Let's check version consistency across related files:
components/webflow_v2/actions/update-collection-item/update-collection-item.mjs (2)
Line range hint 9-94: Implementation looks good!
The core functionality maintains:
- Proper field validation
- Comprehensive error handling
- Clear documentation
- Clean separation of concerns
1-1: Verify the imported module exists
The import path has been updated to reference the v2 version of the Webflow app.
✅ Verification successful
Import path is valid and module exists
The import path ../../webflow_v2.app.mjs correctly resolves to the existing module at components/webflow_v2/webflow_v2.app.mjs.
🏁 Scripts executed
The following scripts were executed for the analysis:
Script:
#!/bin/bash
# Description: Verify the existence of the imported module
# Expected: The file should exist in the components directory
fd -t f "webflow_v2.app.mjs" components/
Length of output: 81
components/webflow_v2/sources/new-collection-item/new-collection-item.mjs (3)
8-8: Version downgrade aligns with revert objective
The version downgrade from "1.0.0" to "0.0.1" is consistent with the PR objective to revert changes from the pre-migration state.
7-7: Documentation link needs review
The documentation link has been changed from the webhooks reference (webhooks/events/collection-item-created) to the item model reference (#item-model). While the item model documentation is relevant, users might miss important webhook-specific information.
5-5: Verify the impact of key identifier change
The change from webflow-new-collection-item to webflow_v2-new-collection-item could potentially break existing integrations. Please ensure that:
- All references to this component are updated
- A migration path exists for existing users
✅ Verification successful
Key identifier change is part of a consistent v2 component structure
The key change from webflow-new-collection-item to webflow_v2-new-collection-item is part of a broader, consistent v2 component structure. The search results show:
- All Webflow v2 components (25+ components) consistently use the
webflow_v2-prefix in their keys - The components are properly organized under the
webflow_v2/directory - No references to the old key format were found in the codebase
This indicates that the key change is intentional and aligns with the established naming convention across all Webflow v2 components.
🏁 Scripts executed
The following scripts were executed for the analysis:
Script:
#!/bin/bash
# Description: Search for any remaining references to the old key identifier
# and verify the existence of migration documentation
# Check for old key references
echo "Checking for old key references..."
rg "webflow-new-collection-item"
# Look for migration guides or documentation
echo "Checking for migration documentation..."
fd -t f "MIGRATION|UPGRADING|README" -X grep -l "webflow.*v2"
Length of output: 264
Script:
#!/bin/bash
# Let's try a broader search strategy to understand the context better
# 1. Search for any Webflow v2 related keys in the codebase
echo "Checking for Webflow v2 component keys..."
rg "key:.*webflow_v2" -A 2
# 2. Look for any references to Webflow versioning or migration
echo "Checking for Webflow version references..."
rg -i "webflow.*v2|webflow.*version" --type md
# 3. Check component structure to understand if this is part of a larger v2 migration
echo "Checking Webflow component structure..."
fd . components/webflow -t d
Length of output: 10609
components/webflow_v2/actions/list-collection-items/list-collection-items.mjs (3)
1-1: Verify the existence of the imported module
The import path has been updated to reference the v2 module. Let's ensure this module exists and is properly referenced.
✅ Verification successful
Import path correctly references an existing module
The import statement references ../../webflow_v2.app.mjs, and verification confirms that the module exists at components/webflow_v2/webflow_v2.app.mjs, making this a valid import path.
🏁 Scripts executed
The following scripts were executed for the analysis:
Script:
#!/bin/bash
# Description: Verify the existence of the webflow_v2.app.mjs module
# Expected: File should exist in the components/webflow_v2 directory
fd -e mjs webflow_v2.app.mjs components/
Length of output: 83
Line range hint 28-32: Verify the listCollectionItems method compatibility
While the core functionality remains unchanged, we should ensure the listCollectionItems method exists in the v2 app module with the same signature.
✅ Verification successful
Method exists and is compatible with the usage
The listCollectionItems method is properly defined in the v2 app module with the same signature, accepting page and collectionId parameters in the same order. The implementation uses the Webflow API client to fetch collection items with proper pagination support via limit and offset parameters.
🏁 Scripts executed
The following scripts were executed for the analysis:
Script:
#!/bin/bash
# Description: Verify the listCollectionItems method in the v2 app module
# Expected: Method should be defined with same parameters
ast-grep --pattern 'listCollectionItems($$$)' components/webflow_v2/webflow_v2.app.mjs
Length of output: 88
Script:
#!/bin/bash
# Let's try a different approach to find the method definition
# First, let's see the content of the app file
cat components/webflow_v2/webflow_v2.app.mjs
# As a backup, let's also search for any method containing "collection" in its name
ast-grep --pattern 'async $METHODNAME($$$) {
$$$
}' components/webflow_v2/webflow_v2.app.mjs | grep -i "collection"
Length of output: 5350
4-4: Verify documentation link accessibility
The component configuration has been updated to reflect the v2 changes. The documentation link points to the general Webflow API docs. Let's verify the link is accessible and correct.
Also applies to: 6-7
✅ Verification successful
Documentation link is valid and follows consistent pattern
The documentation link is correctly embedded in the description field and points to the official Webflow API documentation at developers.webflow.com. The version change to 0.0.1 is also consistent with most other v2 components, with only one component (update-item-inventory) having a different version.
🏁 Scripts executed
The following scripts were executed for the analysis:
Script:
#!/bin/bash
# Description: Verify if other components follow the same versioning pattern
# Expected: All v2 components should use version 0.0.1
# Check for version consistency across v2 components
rg -U 'version: "([^"]+)"' components/webflow_v2/actions/
Length of output: 1621
Script:
#!/bin/bash
# Check the documentation link in the component
rg -U 'doc: "([^"]+)"' components/webflow_v2/actions/list-collection-items/list-collection-items.mjs
# Check documentation links in other v2 components for consistency
rg -U 'doc: "([^"]+)"' components/webflow_v2/actions/
Length of output: 158
Script:
#!/bin/bash
# Let's try a different pattern to find documentation links
rg -U 'documentation: "([^"]+)"' components/webflow_v2/actions/list-collection-items/list-collection-items.mjs
# Check for any variations of documentation links in v2 components
cat components/webflow_v2/actions/list-collection-items/list-collection-items.mjs | grep -i "doc"
Length of output: 340
components/webflow_v2/actions/publish-site/publish-site.mjs (3)
Line range hint 9-33: LGTM! Core functionality preserved
The props configuration and run method remain unchanged, maintaining the same behavior for site publishing functionality.
4-4: Verify documentation link accessibility
The component metadata has been updated to reflect v2 versioning and documentation changes.
Also applies to: 6-7
✅ Verification successful
Component metadata changes are consistent and documentation link is accessible
The verification shows:
- Version "0.0.1" is consistently used across all Webflow v2 components
- The "webflow_v2-" key prefix pattern is uniformly applied across all components
- The documentation link is accessible (HTTP 200 response)
🏁 Scripts executed
The following scripts were executed for the analysis:
Script:
#!/bin/bash
# Description: Check if similar version changes exist in other Webflow v2 components
# Check for consistent versioning across v2 components
fd -e mjs -p "components/webflow_v2/actions" -x grep -l "version: \"0.0.1\""
# Check for consistent key naming pattern
fd -e mjs -p "components/webflow_v2/actions" -x grep -l "key: \"webflow_v2-"
# Verify documentation link format consistency
curl -s -I "https://developers.webflow.com/#publish-site"
Length of output: 3190
1-1: Verify webflow_v2.app.mjs module existence and compatibility
The import path has been updated to reference the v2 version of the app module.
✅ Verification successful
Let me verify the actual content of the webflow_v2.app.mjs file to ensure it has the required exports.
Import path is valid and module maintains required functionality
The webflow_v2.app.mjs module exists and exports the required publishSite method with the expected signature, maintaining API compatibility. The import statement in publish-site.mjs is correct and will work as expected.
🏁 Scripts executed
The following scripts were executed for the analysis:
Script:
#!/bin/bash
# Description: Verify the existence of webflow_v2.app.mjs and check its exports
# Check if the file exists
fd -p "components/webflow_v2/webflow_v2.app.mjs$"
# Check the exports to ensure API compatibility
ast-grep --pattern 'export default {
$$$
publishSite($$$) {
$$$
}
$$$
}'
Length of output: 179
Script:
#!/bin/bash
# Check the content of webflow_v2.app.mjs
cat components/webflow_v2/webflow_v2.app.mjs
Length of output: 5232
components/webflow_v2/actions/update-order/update-order.mjs (2)
Line range hint 9-52: LGTM! Core functionality remains intact
The props configuration and run method are well-structured and maintain the expected functionality for updating Webflow orders.
1-1: Verify the webflow_v2 app module exists
The import path has been updated to reference the v2 version of the app module.
✅ Verification successful
Import path is valid and correctly references the existing module
The import statement correctly references the webflow_v2.app.mjs module, which exists at components/webflow_v2/webflow_v2.app.mjs.
🏁 Scripts executed
The following scripts were executed for the analysis:
Script:
#!/bin/bash
# Description: Verify the existence of the webflow_v2 app module
# Expected: File should exist in the components/webflow_v2 directory
fd -t f "webflow_v2.app.mjs" components/webflow_v2
Length of output: 91
components/webflow_v2/sources/new-form-submission/new-form-submission.mjs (2)
6-6: LGTM: Component key properly updated for v2
The key change maintains consistency with the new versioning scheme and component structure.
8-8: Verify documentation link change
The documentation link now points to a more general section about trigger types instead of the specific form submission event documentation. While both are valid, the specific documentation might be more helpful for users.
✅ Verification successful
Documentation link change appears valid
Both the specific form submission documentation URL and the general trigger types URL are accessible. Since this is a revert PR and both URLs are valid and functional, the change to use the more general documentation section appears intentional. The general trigger types section still provides relevant context about form submissions while potentially offering users a broader understanding of the available triggers.
🏁 Scripts executed
The following scripts were executed for the analysis:
Script:
#!/bin/bash
# Description: Check if the old documentation link is still valid and compare content
# Check if the old URL is still accessible
curl -s -I "https://developers.webflow.com/data/reference/webhooks/events/form-submission" | head -n 1
# Check if the new URL is accessible
curl -s -I "https://developers.webflow.com/#trigger-types" | head -n 1
Length of output: 199
Script:
#!/bin/bash
# Let's check the git history to understand if this is a revert and what was the original link
git log -p -- components/webflow_v2/sources/new-form-submission/new-form-submission.mjs | grep -A 2 -B 2 "description.*form.*submit"
Length of output: 0
components/webflow_v2/actions/update-item-inventory/update-item-inventory.mjs (4)
6-6: Verify the updated documentation link
The documentation link format has been changed. Please verify that the new link https://developers.webflow.com/#update-item-inventory is accessible and points to the correct documentation.
Consider adding a note about the API version in the description to make it clear this is for the v2 API.
- description: "Update the inventory of a specific item. [See the docs here](https://developers.webflow.com/#update-item-inventory)",
+ description: "Update the inventory of a specific item using Webflow API v2. [See the docs here](https://developers.webflow.com/#update-item-inventory)",1-1: Verify the existence of the imported module
The import path has been updated to reference the v2 module.
✅ Verification successful
Import path is valid and module exists
The referenced module webflow_v2.app.mjs exists at the correct location in the components/webflow_v2 directory, confirming that the import statement is valid.
🏁 Scripts executed
The following scripts were executed for the analysis:
Script:
#!/bin/bash
# Description: Verify the existence of the webflow_v2.app.mjs module
# Expected: File should exist in the components/webflow_v2 directory
fd -t f "webflow_v2.app.mjs" components/webflow_v2
Length of output: 91
8-8: Consider updating the version number
Given this is part of a v2 migration, consider if the version number should be updated to reflect this major change.
4-4:
The key change from webflow-update-item-inventory to webflow_v2-update-item-inventory is a breaking change that could affect existing integrations. Please ensure this change is properly communicated to users and that appropriate migration guides are provided.
components/webflow_v2/actions/unfulfill-order/unfulfill-order.mjs (3)
Line range hint 9-31: Implementation looks good
The props structure and run method implementation remain unchanged and follow best practices:
- Clear property definitions using propDefinitions
- Proper async/await usage
- Meaningful success message in the export summary
- Clean return of the API response
1-1: Verify webflow_v2.app.mjs module compatibility
The import path has been updated to use the v2 module. Let's verify the existence and compatibility of this module.
✅ Verification successful
Let me gather more information about the module's compatibility by checking its usage in the unfulfill-order action.
Import path is correctly aligned with the v2 module structure
The import path ../../webflow_v2.app.mjs is verified to be correct and consistent:
- The module exists at the expected location
- It exports the required app interface with proper type and propDefinitions
- The same import pattern is consistently used across all v2 components (19 files)
- The module structure aligns with the v2 migration objective
🏁 Scripts executed
The following scripts were executed for the analysis:
Script:
#!/bin/bash
# Description: Verify the existence of webflow_v2.app.mjs and check its exports
# Check if the file exists
fd -e mjs "webflow_v2.app.mjs$" components/
# Check the exports to ensure they match what's being used
rg -A 10 "export default" components/webflow_v2/webflow_v2.app.mjs
Length of output: 500
Script:
#!/bin/bash
# Check how the app module is used in unfulfill-order.mjs
rg -A 5 "import app" components/webflow_v2/actions/unfulfill-order/unfulfill-order.mjs
# Check if there are any other files using this module to verify consistency
rg "import.*webflow_v2\.app" components/webflow_v2/
Length of output: 2461
4-7: Verify version consistency across v2 components
The version has been downgraded to 0.0.1, which seems unusual for a revert. Let's verify if this version is consistent with other v2 components.
components/webflow_v2/actions/list-orders/list-orders.mjs (3)
1-1: Verify the new import path exists
The import path has been updated to reference the v2 version of the app module.
✅ Verification successful
Import path is valid and compatible
The import path ../../webflow_v2.app.mjs correctly references the existing app module, which provides all the necessary exports and methods required for the list-orders functionality, including the listOrders method used by this action.
🏁 Scripts executed
The following scripts were executed for the analysis:
Script:
#!/bin/bash
# Verify the existence and exports of the new app module
fd -e mjs -e js "webflow_v2.app" components/
Length of output: 85
Script:
#!/bin/bash
# Check the content of the app module to verify exports
cat components/webflow_v2/webflow_v2.app.mjs
Length of output: 5232
5-8: Verify version alignment across components
The significant version downgrade to 0.0.1 and the addition of the _v2 suffix indicate a major change in versioning strategy.
✅ Verification successful
Let me gather more information about the versioning across all webflow_v2 action components specifically.
Let me check the version field specifically in one of these action files to understand the pattern better.
Version 0.0.1 is consistent across webflow_v2 actions
The version 0.0.1 is consistently used across all checked webflow_v2 actions, indicating this is an intentional versioning strategy for the new v2 components. While the package.json shows 0.1.0, individual actions are correctly versioned at 0.0.1 for their initial release. The documentation link is also valid and accessible.
🏁 Scripts executed
The following scripts were executed for the analysis:
Script:
#!/bin/bash
# Check version consistency across webflow_v2 components
echo "Checking versions in webflow_v2 components..."
rg '"version":\s*"[^"]*"' components/webflow_v2/
# Verify documentation link
echo "Checking documentation link validity..."
curl -s -I "https://developers.webflow.com/#get-all-orders"
Length of output: 943
Script:
#!/bin/bash
# Check versions in all webflow_v2 action files
echo "Checking versions in webflow_v2 action files..."
rg '"version":\s*"[^"]*"' components/webflow_v2/actions/ -A 1 -B 2
# List all action files to ensure we're not missing any
echo -e "\nListing all action files:"
fd . components/webflow_v2/actions/ -e mjs
Length of output: 1538
Script:
#!/bin/bash
# Check the content of a few action files to see their version fields
echo "Checking create-collection-item action..."
cat components/webflow_v2/actions/create-collection-item/create-collection-item.mjs | head -n 10
echo -e "\nChecking get-collection action..."
cat components/webflow_v2/actions/get-collection/get-collection.mjs | head -n 10
echo -e "\nChecking update-order action..."
cat components/webflow_v2/actions/update-order/update-order.mjs | head -n 10
Length of output: 1421
Line range hint 24-35: Verify API compatibility with v2
While the implementation remains unchanged, we should verify that the listOrders method signature in webflow_v2 maintains compatibility.
✅ Verification successful
Based on the gathered information, I can now generate the final response:
API compatibility with v2 is verified and correct
The implementation is compatible as:
- The
listOrdersmethod in webflow_v2.app.mjs accepts the expected parameters:{ page: offset = 0, siteId, status } - The action component correctly passes these parameters by spreading the
dataobject which contains:- Required
siteIdfrom props - Optional
statusfrom props
- Required
- The method returns an array of orders as expected, which is correctly handled in the response summary
🏁 Scripts executed
The following scripts were executed for the analysis:
Script:
#!/bin/bash
# Check listOrders method implementation in v2
ast-grep --pattern 'listOrders($_) {
$$$
}' components/webflow_v2/
Length of output: 70
Script:
#!/bin/bash
# Let's try a different approach to find the listOrders method
# First, let's search for files that might contain the implementation
rg -l "listOrders" components/webflow_v2/
# Then let's look at the actual implementation with context
rg "listOrders" components/webflow_v2/ -B 2 -A 5
Length of output: 2792
Script:
#!/bin/bash
# Let's check the props/parameters definition in the list-orders component
rg -B 10 "run\({ \$ }\)" components/webflow_v2/actions/list-orders/list-orders.mjs
Length of output: 185
Script:
#!/bin/bash
# Let's check the props/parameters definition in the list-orders component with fixed regex
rg -B 10 'run\(\{.*\$.*\}\)' components/webflow_v2/actions/list-orders/list-orders.mjs
# Also let's check the entire file content to see the props definition
cat components/webflow_v2/actions/list-orders/list-orders.mjs
Length of output: 1252
components/webflow_v2/actions/list-sites/list-sites.mjs (2)
1-1: Verify the webflow_v2 app module existence and compatibility
The import path has been updated to use the v2 module. Let's verify its existence and implementation.
✅ Verification successful
Import path is correct and module is fully compatible
The webflow_v2.app.mjs module exists and contains the required listSites() method implementation. The import is being used consistently across all v2 components, and the module provides all necessary functionality for the list-sites action.
🏁 Scripts executed
The following scripts were executed for the analysis:
Script:
#!/bin/bash
# Description: Verify the existence and implementation of the webflow_v2 app module
# Expected: Find the app module and its listSites method
# Check if the v2 app module exists
fd webflow_v2.app.mjs
# Verify the listSites method implementation
ast-grep --pattern 'listSites() {
$$$
}'
Length of output: 109
Script:
#!/bin/bash
# Let's examine the content of the webflow_v2 app module to verify the listSites method
cat components/webflow_v2/webflow_v2.app.mjs
# Also check for any other files that might be importing this module
rg "from.*webflow_v2.app" -g '!*.md'
Length of output: 7357
Line range hint 1-18: Verify the impact of this revert operation
As this file is part of a revert operation from PR #14826, let's ensure all necessary changes are properly reverted and won't cause breaking changes for existing integrations.
✅ Verification successful
The revert operation appears to be clean and consistent
Based on the verification results:
- All actions in the webflow_v2 component consistently import from
webflow_v2.app.mjs - No references to the old webflow app were found
- All component keys follow the
webflow_v2-prefix pattern - The component uses the official
webflow-apipackage
🏁 Scripts executed
The following scripts were executed for the analysis:
Script:
#!/bin/bash
# Description: Verify the completeness of the revert operation
# Expected: No remaining references to the old webflow module in v2 components
# Check for any remaining references to the old webflow module
rg "from \"../../webflow.app" components/webflow_v2/
# Check for any mixed usage of old and new keys
rg "webflow-" components/webflow_v2/
Length of output: 238
Script:
#!/bin/bash
# Let's verify the import statements and keys in the v2 components
rg "webflow_v2-" components/webflow_v2/ -A 2
# Check the app import pattern in other v2 actions
fd . components/webflow_v2/actions/ -t f -e mjs --exec grep -l "import.*app.*from.*webflow_v2"
Length of output: 11567
Script:
#!/bin/bash
# Let's check the actual import statements in the actions to verify consistency
fd . components/webflow_v2/actions/ -t f -e mjs --exec head -n 1
# Also check if there are any references to the old webflow app
rg "webflow\.app" components/webflow_v2/
Length of output: 933
components/webflow_v2/actions/list-collections/list-collections.mjs (2)
1-1: Verify the imported module exists
The import path has been updated to reference the v2 module. Let's ensure this module exists and is properly structured.
✅ Verification successful
Import path is valid and module is properly structured
The import path ../../webflow_v2.app.mjs correctly references an existing module that exports the necessary functionality. The module is well-structured with proper exports including methods for handling collections, which are required by the list-collections component.
🏁 Scripts executed
The following scripts were executed for the analysis:
Script:
#!/bin/bash
# Check if the webflow_v2.app.mjs file exists and verify its exports
fd -e mjs -p "webflow_v2.app.mjs$" --exec cat {} \;
Length of output: 5242
Line range hint 9-24: Verify API endpoint compatibility with Webflow v2
While the core functionality remains unchanged, please confirm that the API endpoints and response handling in listCollections method are compatible with the v2 version.
components/webflow_v2/actions/get-site/get-site.mjs (3)
1-1: Verify the existence of webflow_v2.app.mjs
The import path has been updated to reference the v2 version of the app module.
✅ Verification successful
Import path is valid and exports are compatible
The import path ../../webflow_v2.app.mjs correctly resolves to an existing module at components/webflow_v2/webflow_v2.app.mjs which exports the expected app configuration with type and propDefinitions.
🏁 Scripts executed
The following scripts were executed for the analysis:
Script:
#!/bin/bash
# Description: Verify the existence of the webflow_v2.app.mjs file
# and check its exports to ensure compatibility
# Check if the file exists
fd -e mjs "webflow_v2.app.mjs$" components/
# Check the exports in the file
rg -A 5 "export default" components/webflow_v2/webflow_v2.app.mjs
Length of output: 274
4-7: Review version numbering strategy
The component uses a v2 prefix in its key but starts at version 0.0.1. This seems inconsistent with semantic versioning practices. Additionally, the documentation link has changed to a different section of the Webflow API docs.
Consider:
- Should the version start at
2.0.0to match the v2 designation? - Verify if the new API documentation link points to the correct and most up-to-date reference.
Line range hint 9-24: Verify revert completeness
Since this PR aims to revert changes from #14826, we should verify that this component's implementation matches its pre-migration state.
components/webflow_v2/actions/get-collection-item/get-collection-item.mjs (4)
Line range hint 9-33: LGTM! Props configuration is well-structured
The props configuration follows a clean dependency chain and properly uses propDefinitions from the app.
Line range hint 34-40: LGTM! Verify method availability
The implementation is clean and follows best practices. Let's verify that the getCollectionItem method exists in the new app file.
✅ Verification successful
Method exists and is properly implemented
The getCollectionItem method is correctly implemented in the app file and is being used appropriately. The method:
- Exists in
webflow_v2.app.mjs - Takes the expected parameters (
collectionId,itemId) - Properly delegates to the Webflow client API
- Is used consistently across multiple actions in the codebase
🏁 Scripts executed
The following scripts were executed for the analysis:
Script:
#!/bin/bash
# Check if getCollectionItem method exists in the app file
ast-grep --pattern 'getCollectionItem($$$) {
$$$
}' components/webflow_v2/webflow_v2.app.mjs
Length of output: 96
Script:
#!/bin/bash
# Let's try a broader search for getCollectionItem method using ripgrep
rg -U "getCollectionItem.*\{[\s\S]*?\}" components/webflow_v2/webflow_v2.app.mjs
# Also search for any references to this method
rg "getCollectionItem" components/webflow_v2/
Length of output: 1058
4-7: Verify component versioning and naming
The component uses webflow_v2 in its key and has version 0.0.1. If this PR is reverting changes:
- Should the key maintain the
_v2suffix? - Is the version downgrade to
0.0.1intentional?
1-1: Verify if this import should be reverted
The import path points to webflow_v2.app.mjs, but since this PR aims to revert changes from #14826, should this be reverted back to webflow.app.mjs?
components/webflow_v2/sources/changed-ecommerce-inventory/changed-ecommerce-inventory.mjs (1)
5-5: Verify version downgrade impact across the codebase
The component key has been updated to use the v2 prefix while the version has been downgraded to 0.0.1. Let's verify this aligns with other components and doesn't break any dependencies.
Also applies to: 8-8
components/webflow_v2/sources/new-site-published/new-site-published.mjs (2)
7-7: Verify documentation link accuracy
The documentation link has been changed to point to a different section (#trigger-types instead of /webhooks/events/site-publish). Please verify:
- The new link contains the necessary information about site publish events
- This aligns with the documentation structure for other v2 components
✅ Verification successful
Documentation link follows consistent pattern and points to correct section
The documentation link change is valid and follows the consistent pattern used across all Webflow v2 components. The search results show that:
- All components use the same base URL
https://developers.webflow.com/ - The
#trigger-typessection is correctly used for webhook-related sources (also used innew-form-submission) - The "See the docs here" text is consistently used across all components
🏁 Scripts executed
The following scripts were executed for the analysis:
Script:
#!/bin/bash
# Check documentation link consistency across v2 components
rg -A 1 "See the docs" --glob "components/webflow_v2/**/*.{mjs,js}"
Length of output: 7093
5-5: Verify version downgrade impact
The significant version downgrade (1.0.0 → 0.0.1) and key change could affect existing workflows. Since this is part of a revert PR, please ensure:
- No existing workflows are referencing the old key
- The version downgrade aligns with semantic versioning principles
Also applies to: 8-8
✅ Verification successful
Version downgrade and key change appear safe
The codebase scan shows that:
- The new key format (
webflow_v2-new-site-published) is only referenced in its own component file - No references to the old key pattern were found in any JS/MJS files
- No references found in documentation or workflow templates
Since this is a revert PR and there are no existing references to either the old or new key formats in other files, the version downgrade and key change should not impact any existing workflows.
🏁 Scripts executed
The following scripts were executed for the analysis:
Script:
#!/bin/bash
# Check for any references to the old key in the codebase
rg "webflow-new-site-published" --type js --type mjs
# Look for any potential workflow templates or documentation referencing this component
rg -l "webflow.*site.*published" -g "*.md" -g "*.json"
Length of output: 137
Script:
#!/bin/bash
# Check for any references to the old key pattern in the codebase with correct file types
rg "webflow.*new.*site.*published" --type-add 'mjs:*.mjs' --type mjs --type js
# Look for any potential workflow templates or documentation referencing this component
fd . -e md -e json -x rg -l "webflow.*site.*published" {}
# Check git history for the specific file to understand the version changes
git log -p -- components/webflow_v2/sources/new-site-published/new-site-published.mjs | head -n 50
Length of output: 254
components/webflow_v2/actions/get-item-inventory/get-item-inventory.mjs (3)
1-1: Verify if this import change aligns with revert intention
The PR is intended to revert changes from #14826, but this import statement is being changed to reference webflow_v2.app.mjs instead of reverting back to the original webflow.app.mjs.
Line range hint 10-41: Verify method compatibility with app implementation
While the implementation remains unchanged, we should verify that the getCollectionItemInventory method exists and maintains the same signature in the referenced app file.
✅ Verification successful
Let me try a different approach to verify the method existence.
Method implementation is compatible and correctly used
The getCollectionItemInventory method exists in the webflow_v2.app.mjs file with the expected signature (collectionId, itemId), and it's being called correctly in the action file with the same parameters. The implementation uses the webflow client's inventory API, which maintains compatibility.
🏁 Scripts executed
The following scripts were executed for the analysis:
Script:
#!/bin/bash
# Check if the method exists in both app files
echo "Checking method in webflow_v2.app.mjs:"
ast-grep --pattern 'getCollectionItemInventory($$$)'
echo "Checking method in original webflow.app.mjs:"
git show main:components/webflow/webflow.app.mjs | ast-grep --pattern 'getCollectionItemInventory($$$)'
Length of output: 381
Script:
#!/bin/bash
# Search for the app file and check its content
echo "Finding webflow_v2 app file:"
fd -e mjs -e js "webflow_v2.app"
echo "\nChecking method implementation:"
rg "getCollectionItemInventory" -A 5
Length of output: 1411
4-7:
Metadata changes appear inconsistent with revert intention
The changes to the action metadata suggest introducing a new v2 version rather than reverting to the previous state:
- Key changed to include
_v2prefix - Version downgraded to
0.0.1 - Documentation URL modified
These changes seem to contradict the PR's objective of reverting changes from #14826.
components/webflow/webflow.app.mjs (1)
Line range hint 1-251: LGTM!
The updates to the Webflow API client integration and method restructuring are correctly implemented and align with the downgrade to webflow-api@1.3.1.
components/webflow/package.json (1)
Line range hint 3-16: Verify the security status of downgraded dependencies
The dependencies @pipedream/platform and webflow-api have been downgraded to older versions. Ensure that these versions are free from known security vulnerabilities and that downgrading does not introduce any issues.
Run the following script to check for vulnerabilities:
components/webflow_v2/actions/get-order/get-order.mjs (1)
Line range hint 1-33: LGTM!
The action has been correctly updated to use webflow_v2.app.mjs, and the versioning and key have been appropriately adjusted.
components/webflow_v2/actions/get-collection/get-collection.mjs (2)
1-1: LGTM: Import path updated correctly
The import path has been updated to reference the new webflow_v2.app.mjs, which aligns with the PR objective of reverting changes.
4-7: Verify documentation link accessibility
While the key and version changes align with the reversion strategy, let's ensure the new documentation link is accessible and points to the correct location.
✅ Verification successful
Documentation link is accessible and valid
The documentation link is accessible and returns a successful HTTP 200 response, confirming it's a valid resource. The content type and security headers indicate it's the official Webflow documentation site.
🏁 Scripts executed
The following scripts were executed for the analysis:
Script:
#!/bin/bash
# Verify the documentation link is accessible
curl -I https://developers.webflow.com/#get-collection-with-full-schema
Length of output: 976
components/webflow_v2/sources/new-ecommerce-order/new-ecommerce-order.mjs (1)
5-5: LGTM: Component metadata updated consistently
The changes to key, version, and documentation link are consistent with the reversion strategy across the webflow_v2 component.
Also applies to: 8-9
components/webflow_v2/actions/fulfill-order/fulfill-order.mjs (1)
1-1: LGTM: Changes align with component-wide updates
The modifications to import path, key, version, and documentation are consistent with the reversion strategy being applied across the webflow_v2 component.
However, let's verify that all references to this action have been updated to use the new key.
Also applies to: 4-4, 6-7
✅ Verification successful
The action key has been properly updated and is correctly referenced
The verification shows that:
- The action's key is correctly set to
webflow_v2-fulfill-order - The app file correctly implements the
fulfillOrdermethod that is used by this action - No references to the old key format were found
- The integration between the action and the app methods is properly maintained
🏁 Scripts executed
The following scripts were executed for the analysis:
Script:
#!/bin/bash
# Search for any remaining references to the old action key
rg "webflow-fulfill-order" --type js
Length of output: 36
Script:
#!/bin/bash
# Search for references to the action key with v2 prefix and without
rg -i "fulfill.?order" --type js -A 2 -B 2
Length of output: 44
Script:
#!/bin/bash
# Let's check the key definition in the action file and search for any references
cat components/webflow_v2/actions/fulfill-order/fulfill-order.mjs
# Also search for any references to fulfill order in the app file
cat components/webflow_v2/webflow_v2.app.mjs
Length of output: 6202
components/webflow_v2/actions/delete-collection-item/delete-collection-item.mjs (1)
1-1: Verify the API version compatibility
The changes appear to be reverting to an older version of the Webflow API:
- Documentation link points to the older API endpoint
- Version has been downgraded from 1.0.0 to 0.0.1
- Import path and key have been updated to use the v2 prefix
Let's verify the API compatibility:
Also applies to: 4-4, 6-7
✅ Verification successful
Import path change is consistent with v2 migration
The changes are part of a proper v2 migration and are consistent across the codebase:
- The import path
webflow_v2.app.mjsis used consistently across all v2 component files (20 files found) - The app file uses the official
webflow-apiclient library and implements all necessary v2 API methods - The version downgrade to 0.0.1 is appropriate for a new major version component
🏁 Scripts executed
The following scripts were executed for the analysis:
Script:
#!/bin/bash
# Check if there are any other files still referencing the new API endpoints
rg -l "developers.webflow.com/data/reference" .
# Check for any remaining v1 references that might need updating
rg -l "webflow\.app\.mjs" --type js
Length of output: 85
Script:
#!/bin/bash
# Let's check for any files importing from webflow_v2.app.mjs
rg -l "webflow_v2\.app\.mjs"
# Check for documentation URLs in webflow related files
fd webflow --type f --exec rg -l "developers\.webflow\.com"
# Check version numbers in webflow v2 files
fd webflow_v2 --type f --exec rg "version:|version ="
# Check the app file itself to understand the API version
cat components/webflow_v2/webflow_v2.app.mjs
Length of output: 6666
components/webflow_v2/actions/create-collection-item/create-collection-item.mjs (1)
1-1: Ensure consistent versioning across components
The changes align with those in delete-collection-item.mjs, showing a consistent pattern of:
- Moving to v2 naming scheme
- Reverting to older API documentation
- Downgrading version number
Let's verify consistency across all Webflow components:
Also applies to: 4-4, 6-7
✅ Verification successful
Let me gather more specific information about the version numbers in the action files and their documentation links.
Let me try a different approach to check the content of these specific files:
Let me check other action files to verify version consistency:
Based on the evidence gathered, I can now provide the final response:
Version and documentation patterns are consistent across components
The changes in create-collection-item.mjs and delete-collection-item.mjs are consistent with other Webflow v2 components:
- All components use the same documentation URL pattern (developers.webflow.com)
- Both files have version "0.0.1", which is appropriate for new v2 components
- The documentation links follow a consistent format across all actions
🏁 Scripts executed
The following scripts were executed for the analysis:
Script:
#!/bin/bash
# Check version numbers across all Webflow v2 components
echo "Checking version numbers in all Webflow v2 components:"
rg '"version":' components/webflow_v2/
# Check for any inconsistent documentation links
echo "Checking documentation links:"
rg -l "developers.webflow.com/" components/webflow_v2/
Length of output: 2180
Script:
#!/bin/bash
# Check version numbers in action files
echo "Version numbers in action files:"
rg '"version":' components/webflow_v2/actions/create-collection-item/create-collection-item.mjs components/webflow_v2/actions/delete-collection-item/delete-collection-item.mjs
# Check documentation links in action files
echo "Documentation links in action files:"
rg "docs:" components/webflow_v2/actions/create-collection-item/create-collection-item.mjs components/webflow_v2/actions/delete-collection-item/delete-collection-item.mjs
Length of output: 506
Script:
#!/bin/bash
# Display the content of both files to examine version and docs
echo "=== create-collection-item.mjs ==="
cat components/webflow_v2/actions/create-collection-item/create-collection-item.mjs
echo -e "\n=== delete-collection-item.mjs ==="
cat components/webflow_v2/actions/delete-collection-item/delete-collection-item.mjs
Length of output: 3151
Script:
#!/bin/bash
# Sample a few more action files to verify version numbers and documentation patterns
echo "=== Checking other action files ==="
for file in $(find components/webflow_v2/actions -name "*.mjs" -type f | head -n 5); do
echo "=== $file ==="
grep -E '"version"|description:' "$file"
done
Length of output: 2509
| description: "Emit new event when a collection item is changed. [See the documentation](https://developers.webflow.com/data/reference/webhooks/events/collection-item-changed)", | ||
| version: "1.0.0", | ||
| description: "Emit new event when a collection item is changed. [See the docs here](https://developers.webflow.com/#model16)", | ||
| version: "0.0.1", |
There was a problem hiding this comment.
💡 Codebase verification
Version inconsistency detected in Webflow v2 components
All Webflow v2 components use version "0.0.1" except for update-item-inventory which uses "0.0.5". This inconsistency should be addressed:
components/webflow_v2/actions/update-item-inventory/update-item-inventory.mjsuses version "0.0.5"- All other components (actions and sources) use version "0.0.1"
🔗 Analysis chain
Verify version downgrade across Webflow components
The version downgrade from 1.0.0 to 0.0.1 appears to be part of the revert operation. Let's verify this is consistent across other Webflow components.
🏁 Scripts executed
The following scripts were executed for the analysis:
Script:
#!/bin/bash
# Description: Check version consistency across Webflow v2 components
# Expected: All components should use version 0.0.1
echo "Checking versions in Webflow v2 components:"
find components/webflow_v2 -type f -name "*.mjs" -exec grep -l "version:" {} \; | while read -r file; do
echo "=== $file ==="
grep "version:" "$file" -A 1
done
Length of output: 8248
| key: "webflow_v2-update-collection-item", | ||
| name: "Update Collection Item", | ||
| description: | ||
| "Update collection item. [See the documentation](https://developers.webflow.com/data/reference/cms/collection-items/bulk-items/update-items)", | ||
| version: "1.0.0", | ||
| "Update collection item. [See the documentation](https://developers.webflow.com/#update-collection-item)", | ||
| version: "0.0.1", |
There was a problem hiding this comment.
💡 Codebase verification
Version inconsistency found in webflow_v2 actions
Most webflow_v2 actions are at version "0.0.1", but there is an inconsistency:
update-item-inventoryis at version "0.0.5"
The version "0.0.1" appears to be the standard version for webflow_v2 actions, making it consistent with the reviewed component. However, the update-item-inventory action should be reviewed to understand why it has a different version number.
🔗 Analysis chain
Verify version consistency across v2 components
The component has been downgraded to version 0.0.1, which is a significant change. This version should be consistent with other webflow_v2 components.
🏁 Scripts executed
The following scripts were executed for the analysis:
Script:
#!/bin/bash
# Description: Check version consistency across v2 components
# Expected: All webflow_v2 components should have the same version
echo "Checking versions in webflow_v2 components:"
rg '"version":\s*"[^"]*"' components/webflow_v2/
Length of output: 204
Script:
#!/bin/bash
# Let's check the version field in all action files within webflow_v2
echo "Checking version field in webflow_v2 action files:"
rg 'version:\s*"[^"]*"' components/webflow_v2/actions/
Length of output: 1729
| key: "webflow_v2-update-order", | ||
| name: "Update Order", | ||
| description: "Update an order. [See the documentation](https://developers.webflow.com/data/reference/ecommerce/orders/update)", | ||
| version: "1.0.0", | ||
| description: "Update an order. [See the docs here](https://developers.webflow.com/#update-order)", | ||
| version: "0.0.1", |
There was a problem hiding this comment.
💡 Codebase verification
Inconsistent versioning found in webflow_v2 components
All components in the webflow_v2 directory follow the correct naming convention with the "webflow_v2-" prefix, but there is an inconsistency in versioning:
- Most components are at version "0.0.1"
- The "update-item-inventory" component is at version "0.0.5"
This inconsistency should be addressed to maintain uniformity across the v2 migration.
🔗 Analysis chain
Verify consistent versioning across webflow_v2 components
The component has been properly renamed with the v2 prefix and version reset to 0.0.1.
🏁 Scripts executed
The following scripts were executed for the analysis:
Script:
#!/bin/bash
# Description: Check for consistency in versioning and naming across webflow_v2 components
# Expected: All components should use webflow_v2 prefix and version 0.0.1
# Check for consistent key naming
echo "Checking component keys:"
rg '"key": "webflow' components/webflow_v2/actions
# Check for consistent versioning
echo -e "\nChecking component versions:"
rg '"version": "' components/webflow_v2/actions
Length of output: 234
Script:
#!/bin/bash
# Let's try a different approach using ast-grep to find component definitions
# First, check for any .mjs files in the webflow_v2 directory
echo "Files in webflow_v2/actions:"
fd -e mjs . components/webflow_v2/actions
echo -e "\nChecking component definitions:"
# Use ast-grep to find object literals containing key and version properties
ast-grep --pattern '{
key: $_,
$$$,
version: $_
}' components/webflow_v2/actions
Length of output: 1531
Script:
#!/bin/bash
# Let's try with ripgrep to search for the component definitions
echo "Checking component keys and versions:"
for file in $(fd -e mjs . components/webflow_v2/actions -E "**/common/**"); do
echo "=== $file ==="
# Search for key and version in each file, showing 4 lines of context
rg -U "key:|version:" "$file" -B 1 -A 2
done
Length of output: 10564
| description: "Emit new event when a form is submitted. [See the documentation](https://developers.webflow.com/data/reference/webhooks/events/form-submission)", | ||
| version: "1.0.0", | ||
| description: "Emit new event when a form is submitted. [See the docs here](https://developers.webflow.com/#trigger-types)", | ||
| version: "0.0.1", |
There was a problem hiding this comment.
💡 Codebase verification
Version inconsistencies detected across Webflow v2 components
- Most components are at version "0.0.1", which aligns with the reviewed file
- However, there are two inconsistencies:
components/webflow_v2/actions/update-item-inventory/update-item-inventory.mjsis at version "0.0.5"components/webflow_v2/package.jsonis at version "0.1.0"
These version mismatches should be addressed to maintain consistency across the Webflow v2 integration.
🔗 Analysis chain
Verify version alignment across components
The version downgrade to "0.0.1" aligns with the revert objective. However, let's verify consistency across related components.
🏁 Scripts executed
The following scripts were executed for the analysis:
Script:
#!/bin/bash
# Description: Check version consistency across Webflow v2 components
# Find and extract versions from all Webflow v2 component files
echo "Checking component versions:"
fd -e mjs -e json . components/webflow_v2 -x grep -l "version" {} \; -exec grep "version" {} \;
Length of output: 2243
Script:
#!/bin/bash
# Description: Check version consistency across Webflow v2 components
# Corrected command to properly extract versions
# Search for version fields in MJS files
echo "=== Versions in MJS files ==="
rg "version: \".*\"" components/webflow_v2 -A 1
# Search for version in package.json
echo -e "\n=== Version in package.json ==="
rg "\"version\":" components/webflow_v2/package.json
Length of output: 4973
| key: "webflow_v2-list-sites", | ||
| name: "List Sites", | ||
| description: "List sites. [See the documentation](https://developers.webflow.com/data/reference/sites/list)", | ||
| version: "1.0.0", | ||
| description: "List sites. [See the docs here](https://developers.webflow.com/#list-sites)", | ||
| version: "0.0.1", |
There was a problem hiding this comment.
💡 Codebase verification
Version inconsistency detected in webflow_v2 components
Most components are at version "0.0.1", but update-item-inventory is at "0.0.5". This inconsistency should be addressed:
components/webflow_v2/actions/update-item-inventory/update-item-inventory.mjs(version: "0.0.5")- All other webflow_v2 components (version: "0.0.1")
🔗 Analysis chain
Verify version consistency across webflow_v2 components
The version has been downgraded to 0.0.1, which is a significant change. This could impact existing integrations.
🏁 Scripts executed
The following scripts were executed for the analysis:
Script:
#!/bin/bash
# Description: Check version consistency across webflow_v2 components
# Expected: All webflow_v2 components should have consistent versioning
# Find all webflow_v2 action files and grep for version
fd -e mjs . components/webflow_v2/actions -x grep -l "version:" {} | xargs grep "version:"
Length of output: 1652
| key: "webflow_v2-list-collections", | ||
| name: "List Collections", | ||
| description: "List collections. [See the documentation](https://developers.webflow.com/data/reference/cms/collections/list)", | ||
| version: "1.0.0", | ||
| description: "List collections. [See the docs here](https://developers.webflow.com/#list-collections)", | ||
| version: "0.0.1", |
There was a problem hiding this comment.
💡 Codebase verification
Version inconsistency detected in Webflow v2 components
All Webflow v2 components are at version "0.0.1" except for update-item-inventory which is at version "0.0.5". This inconsistency should be addressed.
components/webflow_v2/actions/update-item-inventory/update-item-inventory.mjs(version: "0.0.5")- All other Webflow v2 components (version: "0.0.1")
🔗 Analysis chain
Verify version consistency across Webflow v2 components
The version has been downgraded to 0.0.1, which is a significant change. Let's ensure all related Webflow v2 components maintain consistent versioning.
🏁 Scripts executed
The following scripts were executed for the analysis:
Script:
#!/bin/bash
# Check version numbers in all Webflow v2 component files
echo "Checking version numbers in Webflow v2 components..."
rg -A 1 'version:' components/webflow_v2/
Length of output: 4859
| name: "E-commerce Inventory Updated", | ||
| description: "Emit new event when an e-commerce inventory level changes. [See the documentation](https://developers.webflow.com/data/reference/webhooks/events/ecomm-inventory-changed)", | ||
| version: "1.0.0", | ||
| description: "Emit new event when an e-commerce inventory level changes. [See the docs here](https://developers.webflow.com/#item-inventory)", |
There was a problem hiding this comment.
Documentation link should point to webhook-specific documentation
The documentation link has been changed to point to the general API documentation (#item-inventory) instead of the webhook-specific documentation (webhooks/events/ecomm-inventory-changed). Since this is a webhook source component, it would be more helpful to link to the webhook-specific documentation.
- description: "Emit new event when an e-commerce inventory level changes. [See the docs here](https://developers.webflow.com/#item-inventory)",
+ description: "Emit new event when an e-commerce inventory level changes. [See the docs here](https://developers.webflow.com/data/reference/webhooks/events/ecomm-inventory-changed)",📝 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. Thoroughly test & benchmark the code to ensure it meets the requirements.
| description: "Emit new event when an e-commerce inventory level changes. [See the docs here](https://developers.webflow.com/#item-inventory)", | |
| description: "Emit new event when an e-commerce inventory level changes. [See the docs here](https://developers.webflow.com/data/reference/webhooks/events/ecomm-inventory-changed)", |
| type: "source", | ||
| key: "webflow-new-site-published", | ||
| key: "webflow_v2-new-site-published", | ||
| name: "Site Published", |
There was a problem hiding this comment.
🛠️ Refactor suggestion
Update source name to follow Pipedream conventions
According to Pipedream's component guidelines, source names should start with "New".
type: "source",
key: "webflow_v2-new-site-published",
- name: "Site Published",
+ name: "New Site Published",
description: "Emit new event when a site is published. [See the docs here]📝 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. Thoroughly test & benchmark the code to ensure it meets the requirements.
| name: "Site Published", | |
| name: "New Site Published", |
🧰 Tools
🪛 GitHub Check: Lint Code Base
[warning] 6-6:
Source names should start with "New". See https://pipedream.com/docs/components/guidelines/#source-name
| const domains = await this.listDomains(siteId); | ||
| return domains.map((id, url) => ({ | ||
| label: url, | ||
| id, | ||
| })); |
There was a problem hiding this comment.
Fix the parameter order in domains.map
In the domains.map function, the parameters id and url are incorrectly ordered. The map method's callback should receive (element, index) as arguments. This may result in label and id being assigned incorrect values.
Apply this diff to correct the parameter order:
- return domains.map((id, url) => ({
- label: url,
- id,
- }));
+ return domains.map((domain) => ({
+ label: domain,
+ id: domain,
+ }));Committable suggestion skipped: line range outside the PR's diff.
| name: "Collection Item Deleted", | ||
| description: "Emit new event when a collection item is deleted. [See the documentation](https://developers.webflow.com/data/reference/webhooks/events/collection-item-deleted)", | ||
| version: "1.0.0", | ||
| description: "Emit new event when a collection item is deleted. [See the docs here](https://developers.webflow.com/#item-model)", |
There was a problem hiding this comment.
🛠️ Refactor suggestion
Update source name to follow naming conventions
According to the guidelines, source names should start with "New". Please update the name property from "Collection Item Deleted" to "New Collection Item Deleted" to comply with the naming convention.
Reverts #14826
Summary by CodeRabbit
Release Notes
New Features
webflow_v2) with enhanced API functionalities.Improvements
Versioning
@pipedream/webflow_v2introduced with updated dependencies.