set the channel description: Channel dedicated for developers contributing to the Konsist project. https://github.com/LemonAppDev/konsist For Konsist support use #konsist channel.

A dedicated dev channel, so we can discuss Konsist related tickets.

cleared channel description

set the channel topic: Contributing together to Konsist https://github.com/LemonAppDev/konsist

is there a ticketing system somewhere?

Many tickets in the backlog already have an assignee. Is this on purpose? Otherwise I'll look into https://lemonappdev.atlassian.net/browse/KON-554

Hey devs 👨‍💻 I have unsigned and refined some of the tickets. I have also added and new

ContributeOpportunity

label, so please feel free to grab any tickets from with

ContributeOpportunity

label when you are ready to help. https://lemonappdev.atlassian.net/issues/?jql=labels%20%3D%20ContributeOpportunity%20ORDER%20BY%20created%20DESC One ticket from the above list requires more engagement. I would like to implement this before the next release (end of the month). This is a bit larger ticket, but it is also straight forward and will allow you understand Konsist code base better. https://lemonappdev.atlassian.net/browse/KON-566 The above tickets are mostly the tickets that are not blocking our "internal release schedule". Fell free to grab any of these tickets (If you are working on a ticket please make sure to get the JIRA access, assign it to yourself, and update the ticket status to

In Progress

). You can also work on another tickets (we have a lot things to do), but this will require more cooperation with me, for example, certain features and planed ahead, certain thins depend on each other, so more work alignment may be required here. If you need any help please to ask here. I am grateful for all of your contributions 🙏 Happy coding. BTW I have merged massive Parent Declarations PR to

develop

branch. This is top 1 feature requested by the community. Now parents are represented as actual KoDeclarations, not as strings. This means that we can for example check if parent interface/class is annotated with annotations

X

and

Y

or verify package of the parent.

Hey We are preparing for the next release, so I would like to clean up existing PRs and merge these contributions: 1. @Mirco Franzek a. https://github.com/LemonAppDev/konsist/pull/730 - All of the checks are failing - it looks like it needs some work. Do you still want to refactor this bit? 2. @Yonatan Karp-Rudin a. https://github.com/LemonAppDev/konsist/pull/724 - How this one is going? Any change you can polish during the weekend?

Any one want's to take a look at spotless ticket? - upg to new version fails https://lemonappdev.atlassian.net/browse/KON-565

@Jonathan Sarco any luck with https://lemonappdev.atlassian.net/browse/KON-544 ?

Just got the idea💡 Before

@Test
fun myTest() {
    Konsist
        .scopeFromProject()
        .classes()
        .withNameEndingWith("UseCase")
        .assertTrue {  }
}

After

fun myTest() = konsistScopeFromProject {
    .classes()
    .withNameEndingWith("UseCase")
}.assertTrue {
    it.resideInPackage("..domain..usecase..")
}

Old API will still work. What do you think? Yes 👍 No 👎?

Hey everyone, I see a weird behaviour with Konsist on my project, I don't know if I'm doing something wrong or is an issue in the library so wanted to make sure. I'm using Hexagonal Architecture and I want to make sure that the layers are following the right dependency flow. The problem is that when I use

dependsOnNothing

or

dependsOn(anything)

function on my

domain

layer, both would work! Here is my project's test file: https://github.com/ali-star/GitHubUsers/blob/konsist/app/src/test/java/alistar/sample/githubusers/ArchitectureTest.kt

Hi @igor.wojda, would like to look into https://lemonappdev.atlassian.net/browse/KON-573

Hi all 👋 I made a contribution about

fullyQualifiedName

which should solve KON-578 (among others) : https://github.com/LemonAppDev/konsist/pull/830 If anyone can review this, it should be quick. Thanks.

Hi @igor.wojda, I would like to help this project. Is the best way to do this to take first ticket from the backlog?

Hey devs I am experiencing the issue where

Konsist

is failing while parsing large amount of classes due to -

Caused by: java.lang.OutOfMemoryError: Java heap space: failed reallocation of scalar replaced objects

. I am struggling to find the root cause of the issue (tried few

gradle.properties

flags but no luck). I guess

Konsist

implementation is not-optimal, but I am not sure how to find root cause of this error. If you want to help please take a look. I am attaching a complete sample project. This is the all in one sample that you can run. it contains: 1.

Konsist 0.14.0

source code (copied to

main

source set instead of dependency) just for debugging convince 2. Generated classes that are parsed by

Konsist

(

parsedClasses

dir) 3. Sample test class (

SampleKonsistTest

) that is parsing classes in

parsedClasses

To reproduce just run

./gradlew --stop && ./gradlew konsistTest --rerun-tasks

command. Perhaps someone has more experience with debugging memory related issues. I would appreciate any help on this.

ℹ️ I opened this pull request to fix CI jobs on macos, since the migration of

macos-latest

github actions image from

macos-14

to

macos-14-arm64

, (where java 8 is no more available in

macos-14-arm64

).