@mfulton26 Thanks for opening the issue. Please share the your eslint.config.mjs and preferably minimal CDK stack code to reproduce the issue. With the below default eslint.config.mjs, the issue is not reproducible:

import globals from "globals";
import pluginJs from "@eslint/js";
import tseslint from "typescript-eslint";


/** @type {import('eslint').Linter.Config[]} */
export default [
  {files: ["**/*.{js,mjs,cjs,ts}"]},
  {languageOptions: { globals: globals.browser }},
  pluginJs.configs.recommended,
  ...tseslint.configs.recommended,
];

Thanks,
Ashish

The @typescript-eslint/no-unsafe-assignment rule needs to be enabled.

Here are some TypeScript ESLint Playground links demonstrating the issue and possible fix:

1. error
2. possible fix

I can create a more in-depth example if still needed but here are better steps to reproduce then I initially provided:

1. set up a new TypeScript project with typescript-eslint
2. set the @typescript-eslint/no-unsafe-assignment to "error"
3. import FilterRule from aws-cdk-lib/aws-lambda
4. use FilterRule.isEqual() in any assignment (e.g. const eventName = FilterRule.isEqual("EVENT_NAME");)

Reproducible after adding "@typescript-eslint/no-unsafe-assignment": "error" to eslint.config.mjs file:

export default [
  {files: ["**/*.{js,mjs,cjs,ts}"]},
  {languageOptions: { globals: globals.browser }},
  pluginJs.configs.recommended,
  ...tseslint.configs.recommendedTypeChecked,
  {
    rules: {
      "@typescript-eslint/no-unsafe-assignment": "error",
    },
    languageOptions: {
      parserOptions: {
        projectService: true,
        tsconfigRootDir: import.meta.dirname,
      }
    }
  }
];

It flags below error in VS Code IDE: