Context
The Node SDK uses ConnectorException following the .NET naming convention. Azure SDK TypeScript guidelines require the Error suffix for all error/exception types.
Issue
// Current (follows .NET convention)
export class ConnectorException extends Error { ... }
// Azure SDK TypeScript guideline
export class ConnectorError extends Error { ... }
The @azure/core-rest-pipeline package uses RestError, not RestException. All Azure SDK JS packages follow the Error suffix consistently.
Proposed change
- Rename
ConnectorException → ConnectorError in src/azureConnectors/connectorException.ts
- Update all imports and
catch clauses across the codebase
- Update the
throw new ConnectorException(...) calls in all 12 generated *Extensions.ts files to throw new ConnectorError(...)
- Update the barrel export in
src/azureConnectors/index.ts
This is a breaking change — coordinate with the @azure/core-rest-pipeline adoption issue where ConnectorError would extend RestError instead of the built-in Error.
Azure SDK guideline
Error naming: use Error suffix
Context
The Node SDK uses
ConnectorExceptionfollowing the .NET naming convention. Azure SDK TypeScript guidelines require theErrorsuffix for all error/exception types.Issue
The
@azure/core-rest-pipelinepackage usesRestError, notRestException. All Azure SDK JS packages follow theErrorsuffix consistently.Proposed change
ConnectorException→ConnectorErrorinsrc/azureConnectors/connectorException.tscatchclauses across the codebasethrow new ConnectorException(...)calls in all 12 generated*Extensions.tsfiles tothrow new ConnectorError(...)src/azureConnectors/index.tsThis is a breaking change — coordinate with the
@azure/core-rest-pipelineadoption issue whereConnectorErrorwould extendRestErrorinstead of the built-inError.Azure SDK guideline
Error naming: use
Errorsuffix