jlleitschuh02/08/2023, 1:57 PM
Sha Sha Chu02/08/2023, 3:34 PM
Emil Kantis02/08/2023, 3:49 PM
Paul Dingemans02/08/2023, 4:31 PM
Sha Sha Chu02/08/2023, 4:32 PM
wakingrufus02/08/2023, 8:55 PM
Paul Dingemans02/08/2023, 9:02 PM
wakingrufus02/09/2023, 3:12 PM
Paul Dingemans02/15/2023, 8:39 PM
. See https://github.com/pinterest/ktlint/blob/master/CHANGELOG.md for a description of the breaking changes. See https://pinterest.github.io/ktlint/install/snapshot-build/ for the snapshot build containing the changes. I am not planning any other breaking changes in this release, unless I encounter obvious mistakes. This would be really a good moment to verify the impact of the changes in
as we can the release within certain limits if that is convenient. Let me know, what I can do to help you in this process. In https://github.com/pinterest/ktlint/milestone/21 you can monitor what other changes I am planning to implement before the next version will be released. I expect this to take between 3 to 8 weeks throughput time.
wakingrufus02/15/2023, 9:51 PM
was all part of 0.48.0 already right?
0.48.2 - 2023-01-21
Paul Dingemans02/18/2023, 11:23 AM
should be taken into account. So in the the markdown file it is line 1 to 228 that describe the breaking changes. Sorry for the inconvenience. I will fix this tomorrow.
## [0.48.2] - Unreleased
wakingrufus02/20/2023, 5:01 PM
? I'd like to avoid parsing the file myself in order pass it in as a EditorConfigDefaults if possible, as it seems like that is not what that param is meant to be used for
Paul Dingemans02/20/2023, 8:48 PM
that does this for you since a couple of releases.
wakingrufus02/20/2023, 9:39 PM
Paul Dingemans02/21/2023, 11:25 AM
it was possible to specify the path to
. The usage of that parameter was however unclear and let to usages in which different API consumers had different expectations about that parameter. So it has been deprecated in
and removed in
. Re-introducing the parameter in the
would re-introduce the old problem so that does not seem the way forward. I don’t know how the plugin usually supports backward compatibility. Can the reflection problem be avoided by exposing some other functionality in a separate module to bridge the gap? This module could for example be maintained until Ktlint 1.0 is release which really seems to be a good to drop the backward compatibility guarantee of he plugin.
wakingrufus02/21/2023, 4:36 PM
Paul Dingemans02/25/2023, 11:10 AM
and rebrand it to
if we would agree on this. How would you feel about that?
wakingrufus02/25/2023, 4:10 PM
Paul Dingemans02/25/2023, 4:19 PM
. Instead we would basically copy a stripped version of the current plugin into the ktlint project without any of the code that is needed to maintain backwards compatibility with older ktlint versions which would not make sense when they are combined in one project. The current plugin project can then become obsolete and frozen at
wakingrufus02/25/2023, 4:22 PM
Paul Dingemans02/25/2023, 4:28 PM
jlleitschuh02/25/2023, 4:29 PM
Paul Dingemans02/25/2023, 4:31 PM
wakingrufus02/25/2023, 4:31 PM
Paul Dingemans02/25/2023, 4:32 PM
wakingrufus02/25/2023, 4:36 PM
Emil Kantis02/25/2023, 4:49 PM
Paul Dingemans02/25/2023, 4:50 PM
wakingrufus02/25/2023, 4:50 PM
Paul Dingemans02/25/2023, 4:57 PM
. Another hurdle is the availability of maintainers. I think it would be great if we can combine forces into a single repository with multiple active maintainers. The number of active maintainers in Ktlint is approximately 1 …
Sha Sha Chu02/25/2023, 5:10 PM
wakingrufus02/25/2023, 6:05 PM
Paul Dingemans02/25/2023, 6:50 PM
version of the API. Lets keep in touch.
wakingrufus02/25/2023, 6:58 PM
Paul Dingemans03/24/2023, 5:01 PM
. Only one issue is left to implement and then regression testing starts. If you would like me to make adjustments to the API of the next release, you should do so asap. I expect to release the next version by the end of next week otherwise. The
release can be seen as a release candidate for the
version. The API for the
should be identical to the
with exception of removal of API’s which will be deprecated in