New version converts `any` to `{}` too aggressively

For code like this:

import {EventEmitter} from 'events';

interface MyData {
  foo: string;
}

class Foo extends EventEmitter {
  on(event: 'mydata', listener: (data: MyData) => void): this;
  on(event: string, listener: (...args: any[]) => void): this {
    return super.on(event, listener);
  }
}

, gts fix converts ...args: any[] to ...args: {}[], which makes the specialized on() method (for ‘mydata’) not compatible with the implementation and makes the build fail. I think this must be left as any[] because the super class (EventEmitter)'s type is any[].

That also brings another problem where the linter complains about {}[], saying that

Array type using ‘T[]’ is forbidden for non-simple types. Use’Array<T>’ instead.

Which forces me to write Array<{}>, which is harder to read than {}[] or any[]. It surprises me that it says {} is of a non-simple type.

[JustinBeckwith]

I’m +1 on this approach - having the lint rule is ok, breaking all of my code when I run fix isn’t.

[ofrobots]

Agree with @calebegg. The no-any rule should not have a fixer.

I propose that we implement our own no-any-google rule that jettisons the fixer and use that instead. Or convince upstream to do it.