Skip to content

> > > > Using 'as any' to test unsupported actions bypasses type safety. Consider using a more type-safe approach or adding a comment explaining why this type assertion is necessary for testing error handling. #139

@joe10832

Description

@joe10832

Using 'as any' to test unsupported actions bypasses type safety. Consider using a more type-safe approach or adding a comment explaining why this type assertion is necessary for testing error handling.

  test("should throw error for unsupported action", async () => {
    // Using 'as any' here to intentionally bypass type safety for testing error handling of unsupported actions.

Originally posted by @joe10832 in #75 (comment)

Metadata

Metadata

Assignees

Labels

documentationImprovements or additions to documentationenhancementNew feature or requesthelp wantedExtra attention is neededquestionFurther information is requested

Type

No fields configured for Bug.

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions