1. It seems like there is a behavior change introd...
# ktlint
2. It seems like there is a behavior change introduced in
, where values passed as
using the now deprecated
method are ignored. Maybe I misread the release notes, but they had vibe you strongly advise to migrate now, because later it be more difficult, but in overall
is still backwards compatible. If breaking the compatibility was intended then I’ll share my personal opinion: I think it would be better for api consumers if you removed the method already in this release so api consumers would get a compile time error, instead of runtime one (or bug reports from end users 😛 ). If breaking the compatibility wasn’t intendent, then FYI it did, at least the case described above 😛