Josh Pike
Josh Pike
We've got our own internal google sheet running which shows the diff between our eslint rules and Rome equivalents, for a model of how to maybe go about things. https://docs.google.com/spreadsheets/d/16PXNlt7XoQG_ByRC9azLcFqPxZbIyppcb2c92O_lCv4/edit?usp=sharing...
I’m incredibly busy… is there some sort of telemetry that could assist in this?
not having this issue anymore. closing
in other news, I've decided to move my whole development team to Rome! I'm fed up with eslint being the memory hog it is, and confident the Rome team are...
I should add the caveat that we're only using the Rome linter for now, as the formatter does not have any visibility on html in angular decorators (like in screenshot)....
my current ugly workaround: ``` const mockRedis = RedisMockClient.createClient(); // promisify mock methods redis = { get: promisify(mockRedis.get).bind(mockRedis), delete: promisify(mockRedis.del).bind(mockRedis), flushAll: promisify(mockRedis.flushall).bind(mockRedis), setEx: promisify(mockRedis.setex).bind(mockRedis), expire: promisify(mockRedis.expire).bind(mockRedis), } as unknown as...
Just ran into a production bug that could have been prevented by this rule. Definitely looking forward to this one
thanks for the heads up, noFallthroughCasesInSwitch works fine.
Awesome, you guys rock!
I'd recommend throwing in a couple of integration tests, including angular