Skip to content

ClientContext should be a type, not String #169

Open
@ktoso

Description

@ktoso

Expected behavior

The ClientContext is often of well known shape:

It should handle the typing more gracefully I think, see docs:
https://docs.aws.amazon.com/lambda/latest/dg/nodejs-context.html

See also: #167 (comment) for discussion on this

Actual behavior

It's a String today:

            let clientContext: String?

Metadata

Metadata

Assignees

No one assigned

    Labels

    kind/enhancementImprovements to existing feature.

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions