@Emil Kantis you closed off the rename inspectors ticket, do you not want to do that anymore ?

There was very little response in favor of doing it (or not doing it for that matter), so I thought we could drop it

My only reluctance was that the new names weren't much better imo

I agree that

forOne

reads better and it’s a lot cleaner. A downside to the aliases would be consistency, and knowing what to prefer.. I still think it would be great for discoverability

The aliases won't hurt

Could adding them as deprecated, with a

ReplaceWith

each respective

forX

version serve a purpose? Or do you think that would be bad practice?

I'm reluctant to keep deprecating things as people put years into tests

I mean that the added aliases would be flagged from the get-go.. 🙂

Oh i see

Ah, that’s probably better

Yep

I really like that idea 🙂

Easy too

I remember seeing something in github regarding someone testing

Boolean?

like

val x: Boolean? = null
x shouldNotBe true

where the plugin suggested that it should be replaced by

x shouldBe false

Did you pick that one up or perhaps that could be.a good thing to check out to learn a bit about the intellij plugin?

I haven't done that one

Odd.. I can’t find it anymore either

It's a stupid rule