Conversation
Bundle ReportChanges will increase total bundle size by 31.17kB (0.07%) ⬆️. This is within the configured threshold ✅ Detailed changes
Affected Assets, Files, and Routes:view changes for bundle: editor-ui-esmAssets Changed:
|
![cubic-dev-ai[bot]](https://avatars.githubusercontent.com/in/1082092?s=60&v=4){kind=small}
Contributor
There was a problem hiding this comment.
No issues found across 4 files
Architecture diagram
sequenceDiagram
participant WF as Workflow Engine
participant Node as AwsS3V2 Node
participant Helpers as GenericFunctions (REST)
participant S3 as AWS S3 API
WF->>Node: execute("bucket:search")
Node->>Helpers: awsApiRequestREST (Get Location)
Helpers->>S3: GET /?location
S3-->>Helpers: XML LocationConstraint
Helpers-->>Node: Region string
Note over Node: NEW: Determine property to extract<br/>based on 'delimiter' AND 'includeCommonPrefixes'
alt returnAll is true
Node->>Helpers: CHANGED: awsApiRequestRESTAllItems()
Note right of Node: Pass 'ListBucketResult.CommonPrefixes' <br/>OR 'ListBucketResult.Contents'
loop Pagination
Helpers->>S3: GET Bucket (ListObjectsV2)
S3-->>Helpers: XML Response
end
Helpers-->>Node: Combined items array
else returnAll is false (Limit set)
Node->>Helpers: awsApiRequestREST()
Helpers->>S3: GET Bucket (ListObjectsV2)
S3-->>Helpers: XML Response
Helpers-->>Node: rawResponse (JSON)
Note over Node: NEW: Extract property from rawResponse
alt CHANGED: Result is single object (xml2js behavior)
Node->>Node: Wrap in Array [item]
else Result is already array
Node->>Node: Keep as Array
else Result is empty
Node->>Node: Return []
end
end
Node-->>WF: Return JSON Array
Codecov Report❌ Patch coverage is
📢 Thoughts on this report? Let us know! |
Contributor
Performance ComparisonComparing current → latest master → 14-day baseline Idle baseline with Instance AI module loaded
Memory consumption baseline with starter plan resources
docker-stats
How to read this table
|
elsmr
approved these changes
Apr 22, 2026
github-merge-queue
Bot
removed this pull request from the merge queue due to failed status checks
…-common-prefixes
n8n-assistant
Bot
added
n8n team
Joffcom
deleted the
node-4853-aws-s3-node-add-option-to-return-common-prefixes
branch
Merged
Contributor
|
Got released with |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Adds an Include Common Prefixes boolean option (default:
false) to the AWS S3 node'sbucket:searchoperation (Additional Fields).When a Delimiter is set (e.g.
/), the S3 ListObjectsV2 API returns two distinct result sets:Contents— individual objects that don't share the delimiter groupingCommonPrefixes— grouped "virtual folder" entries (e.g.photos/,logs/)Previously the node always returned
Contentsonly. With this option enabled, the node returnsCommonPrefixesinstead, allowing users to do shallow directory-style listings.Changes:
includeCommonPrefixesfield inadditionalFields(description notes it only works when Delimiter is set)returnAlland paginated paths respect the new optionelsebranch (correctness fix)bucket:searchoperation (6 test cases)How to test:
bucket:searchoperation/) and a Prefix pointing at a "folder"{ Prefix: "..." }entries{ Key: "...", Size: "..." }entriesImages showing it in action:
Related Linear tickets, Github issues, and Community forum posts
https://linear.app/n8n/issue/NODE-4853
Review / Merge checklist
Backport to Beta,Backport to Stable, orBackport to v1(if the PR is an urgent fix that needs to be backported)🤖 PR Summary generated by AI