Skip to content

Assert error after enabling cypress #66

@jojozhuang

Description

@jojozhuang

After enabling cypress(see PR #65):

  • npm run build is ok
  • npm run test:headless is ok
  • npm run e2e:headless is ok.

However, npm run lint has errors. Have to add the following rules into eslint.config.mjs to ignore the errors.

        "@typescript-eslint/no-unsafe-call": "off",
        "@typescript-eslint/no-unsafe-member-access": "off",

In addition, I see `Property 'toBeTruthy' does not exist on type 'Assertion' error in VSCode.
Image

The issue is that Cypress types are overriding Jasmine types because Cypress also has its own expect assertions.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions