[Feature]: Use default imports to minimize identifier conflicts with existing code

[trivikr]

Self-service

• I'd be willing to implement this feature

Input code

Input:

import DynamoDB from "aws-sdk/clients/dynamodb";

const ddbClient = new DynamoDB({ region: "us-west-2" });
const listTablesInput: DynamoDB.ListTablesInput = { Limit: 10 };
const listTablesOutput: DynamoDB.ListTablesOutput = await ddbClient
  .listTables(listTablesInput)
  .promise();

Existing output:

import { DynamoDB, ListTablesCommandInput, ListTablesCommandOutput } from "@aws-sdk/client-dynamodb";

const ddbClient = new DynamoDB({ region: "us-west-2" });
const listTablesInput: ListTablesCommandInput = { Limit: 10 };
const listTablesOutput: ListTablesCommandOutput = await ddbClient
  .listTables(listTablesInput);

Expected Output

import * as DynamoDB from "@aws-sdk/client-dynamodb";

const ddbClient = new DynamoDB.DynamoDB({ region: "us-west-2" });
const listTablesInput: DynamoDB.ListTablesCommandInput = { Limit: 10 };
const listTablesOutput: DynamoDB.ListTablesCommandOutput = await ddbClient.listTables(
  listTablesInput
);

Additional context

This solution not only minimizes imports which can conflict with other variables defined in the code, but also adds support for nested type definitions requested in #225

[trivikr]

An attempt of implementation was made in #240

An easier solution would be to use named import for client creation and other direct uses of Identifier (like instanceof checks), and default import for TSQualified names.

import AWS_DynamoDB, { DynamoDB } from "@aws-sdk/client-dynamodb";

const ddbClient = new DynamoDB({ region: "us-west-2" });
const listTablesInput: AWS_DynamoDB.ListTablesCommandInput = { Limit: 10 };
const listTablesOutput: AWS_DynamoDB.ListTablesCommandOutput = await ddbClient.listTables(
  listTablesInput
);

[trivikr]

An easier solution would be to use named import for client creation and other direct uses of Identifier (like instanceof checks), and default import for TSQualified names.

During internal discussions, we decided to go ahead with this suggestion.

[github-actions]

This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs and link to relevant comments in this thread.