linter | A Base Linter with Cow Powers http : //steelbrain.me/linter/ | Code Analyzer library

I have this error reported by the linter on the call to _.isEqual :

https://github.com/typescript-eslint/typescript-eslint/blob/v4.22.0/packages/eslint-plugin/docs/rules/unbound-method.md

Do you know how I can correct this error?

I want to make sure that any pull request in my Github repo follows the rules defined in .editorconfig (ASp.NET Core 5 C# project). I have found https://github.com/github/super-linter to lint the code using,

I have added the below linter.yml file in my workflow,

I'm having some issues with attempting to do TypeScript typeguarding. Basically what I want to do check if path[aPath] is an array containing elements of type Type1, and then push onto that array. However, I'm not able to do this even after checking whether the value is an array or not with Array.isArray(). Obviously I'm doing some wrong with type-guarding, and maybe what I'm doing isn't type guarding at all, so some feedback and maybe a solution would be amazing.

If this helps, hovering over path[aPath].push(...) the linter gives this error:

This expression is not callable. Not all constituents of type 'Type1[] | ((...items: Type1[]) => number)' are callable. Type 'Type1[]' has no call signatures.ts(2349)

After upgrading an angular nx workspace to the latest version 12.3.4 and converting the projects from tslint to eslint, I'm not able to generate components anymore.

When running nx g c shells/root --project=test-app for example, an error is thrown saying 'styleext' is not found in schema. Within the angular.json file, the following schematics are defined at the beginning:

I'd like to enforce PascalCase for variables of type JSX.Element in my React+Typescript project. I frequently use the following pattern to create functional components, and I like to distinguish my eponymous export by giving it a PascalCase name:

I am using Go 1.16.4. I am trying to deal with such code:

I have a boolean valued input property in an Angular 12 app that looks like this:

So far I've been unable to figure out a ready to use solution for throwing an error if something does a default export.

We internally have the standard to only do named exports, but I'd like the linter to ensure it doesn't happen.

Is there a way to accomplish this short of writing a custom rule?

EDIT: I'm assuming, but could very easily be wrong, that I could use the no-restricted-syntax rule like I was pointed to here. I just didn't want to reach for that if there was a better solution.

I'm trying to return a user of type UserRecord after saving to database, but getting a linting error because getUserByUuid returns Promise so the linter is returning an error because I'm trying to return a type for createUser which returns Promise. I've tried to type assert it user! but it's not working. I'm checking it in the null check right before the return but the linter isn't picking it up. What's the best way to handle this situation?