1.8 gradle plugin introduces breaking change in `cssSupport` changing `enabled` from field to proper...

# eap

[altavir]

1.8 gradle plugin introduces breaking change in cssSupport changing enabled from field to property without proper documentation.

[tapchicoma]

cc @Ilya Goncharov [JB]

[altavir]

cssSupport{
    enabled.set(true)
}

looks ugly by the way

[tapchicoma]

it is Gradle API, should be better in ~Gradle 8.1

[altavir]

I know. But it is a breaking change. For people not as familiar with gradle as I am, it could be very uncomfortable. It is quite easy to add enable/disable methods as temporary workaround.

[tapchicoma]

in Groovy you don't need to use .set() - enabled = true should work as well

[altavir]

Nobody uses groovy API nowadays.

[efemoney]

Tons of people still use the groovy API (I personally don’t). I for one welcome the breaking change and like @tapchicoma mentioned it will be automatically better in Gradle 8.

Personally, I disagree with adding enable accessors temporarily just because its bloat and will need to be supported for longer. I agree that it should be documented somewhere however

[tapchicoma]

it is Gradle API, should be better in ~Gradle 8.1

By this I meant that starting from this release your .kts code should be the same as in Groovy for Gradle Properties API:

cssSupport.enabled = true