Daniel Nixon

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 =...

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

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...

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,...

1. If the left and right type are the same, it suggests the either is being used as a union and should be replaced with a simple union `a |...

```ts const target = { a: "hello", }; const handler = { get() { return 42; }, }; const proxy2 = new Proxy(target, handler); // Explodes at runtime proxy2.a.toUpperCase(); ```

https://github.com/gvergnaud/ts-pattern#run throws, replace with `exhaustive` or `otherwise`.

Update to reflect that React Router now supports scroll restoration

1

At the time I created this library, React Router (v5? v4?) had no support for scroll restoration. It does now (see https://reactrouter.com/en/6.6.2/start/overview#scroll-restoration). * Does this conflict with what oaf-react-router does?...

[Docs]: Reconsider recommendation to use the browser's built in HTML Form Validation

5

### What version of React Router are you using? NA ### Steps to Reproduce Read https://reactrouter.com/en/main/components/form ### Expected Behavior Please reconsider recommending the browser's native form validation, which is known...