aws / aws/aws-toolkit-vscode

Additional Lambda Handler detection for setting module.exports to an object

Open
#143 0 comments 0 reactions 0 assignees View on GitHub
feature-request language:node
Dominant language
TypeScript
Stars
2k
Forks
807
Avg merge
10h 12m
Merged PRs (30d)
7

Description

**Is your feature request related to a problem? Please describe.**

Extend the javascript Lambda Handler candidate detection from Issue #140 PR #142 to support the following scenarios:

```typescript
const myExports = {
foo: // ...
bar: // ...
}

[module.]exports = myExports

// and

[module.]exports = {
foo: // ...
bar: // ...
}
```

**Describe the solution you'd like**

Where `foo` and `bar` are valid candidates for Lambda function handlers, they are detected with the rest of the candidates.

**Describe alternatives you've considered**

**Additional context**

Contributor guide

Open the contributing guide

Research direction

Review the JavaScript Lambda handler detection work from Issue #140 and PR #142 first. Extend the existing candidate-detection path to cover an object assigned through a variable and an object assigned directly to module.exports or exports. Done when valid foo and bar handlers in both examples are detected with the existing candidates.

Written by the indexing model from the issue text.

Assessment

Tech stack
javascript, typescript
Domain
cloud, tooling
Issue type
Feature
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
45/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.