eslint-plugin-total-functions

eslint-plugin-total-functions copied to clipboard

prefer-immutable-types causes ESLint to crash on matrices

1

```ts const myFunction = (x: number[][]): string => { return 0; }; ``` Causes the rule to crash: ``` Oops! Something went wrong! :( ESLint: 8.56.0 RangeError: Maximum call stack...

Tim-W-James

This PR contains the following updates: | Package | Type | Update | Change | |---|---|---|---| | [actions/setup-node](https://togithub.com/actions/setup-node) | action | major | `v3` -> `v4` | --- ### Release...

renovate[bot]

Bump semver from 5.7.1 to 5.7.2

1

Bumps [semver](https://github.com/npm/node-semver) from 5.7.1 to 5.7.2. Release notes Sourced from semver's releases. v5.7.2 5.7.2 (2023-07-10) Bug Fixes 2f8fd41 #585 better handling of whitespace (#585) (@​joaomoreno, @​lukekarrys) Changelog Sourced from semver's...

dependabot[bot]

[total-functions/no-unsafe-readonly-mutable-assignment] False positive?

2

Hi, I'm getting the following error: ``` 25:3 error Unsafe "Mutable" to "Mutable" assignment. Source: "{ c: number; } | {}", destination: "{ c: number; } | { c?: undefined;...

ryb73

Prefer https://github.com/Effect-TS/effect or https://gcanti.github.io/fp-ts/modules/TaskEither.ts.html

danielnixon

no-unsafe-type-assertion: redundant thanks to `satisfies`?

1

See https://github.com/microsoft/TypeScript/issues/47920 and https://www.typescriptlang.org/docs/handbook/release-notes/typescript-4-9.html#the-satisfies-operator

danielnixon

no-unsafe-readonly-mutable-assignment failing to identify a ReadonlyShallow correctly

1

This is working: ```ts type Thing = { a: string }; type OtherThing = { readonly a: string }; // This is correctly inferred to be ReadonlyShallow type ThingArray =...

danielnixon

New rule: skipLibCheck must be false

2

> This can save time during compilation at the expense of type-system accuracy. https://www.typescriptlang.org/tsconfig/skipLibCheck.html

danielnixon

New rule: prevent unsafe assignment of fp-ts types

2

```ts export const foo: IO = () => "hello"; // These assignments compile because the types are compatible, but the semantics are such that doing so is almost certainly an...

danielnixon

Some codebases will have embraced TaskEither and friends but will not have adopted a hard-line stance against impure logging. In these codebases, imperative logging is tolerated. Fine you might say,...

danielnixon