Update on that issue if I do `build` the problem comes back kotlinlang #arrow-contributors

Channels

100daysofcode

100daysofkotlin

100daysofkotlin-2021

androidgithubprojects

cincinnati-user-group

competitive-programming

event21-community-content

java-to-kotlin-refactoring

jvm-ir-backend-feedback

kotlin-multiplatform-contest

kotlinultimatechallenge

myndocs-oauth2-server

naming

navigation-architecture-component

practical-functional-programming

proguard

prozis-android-backup

refactoring-to-kotlin

russian-kotlinasfirst

skia-wasm-interop-temp

stayhungrystayfoolish

swagger-gradle-codegen

tricity-kotlin-user-group

Title

pablisco

01/20/2018, 2:25 PM

Update on that issue, if I do

build

the problem comes back up. I have to do

clean build

¯\_(ツ)_/¯

mkobit

01/20/2018, 8:16 PM

I think that is because detekt finds all the generated classes in the second build

pablisco

01/21/2018, 10:27 AM

Makes sense :)

Regarding this issues. Should we try to make sure the code generated by ank also passes detekt? Would make it easier to rebuild while development

mkobit

01/22/2018, 2:46 PM

that and/or skipping generated classes

pablisco

01/22/2018, 3:31 PM

Ah! on the TO-DO list: https://github.com/arrow-kt/arrow/issues/181

mkobit

01/22/2018, 3:44 PM

good find!

pablisco

01/22/2018, 3:58 PM

Also, running

clean assemble

is much easier when building broken code so the tests don't fail and a wee faster

And feels like one is in the Avengers

3 Views

#arrow-contributors Join Slack