Platform (jvm, js, android): jvm
Extension (none, kotlin 1.3, jdk8): none
We want to migrate the api-cc-infix-en_GB... modules which are based on Assert to Expect. We have already created the corresponding
modules api-infix-en_GB.... Also there are already fluent-en_GB... modules where we have already done the transition from Assert to Expect
Following the things you need to do:
mapEntryAssertions.kt from atrium-api-fluent-en_GB-common to atrium-api-infix-en_GB-commonisKeyValue instead of two parameters (see mapEntryAssertions.kt in atrium-api-cc-infix-en_GB-common for a guideline)MapEntryAssertionsSpec.kt from atrium-api-fluent-en_GB-common to atrium-api-infix-en_GB-commonKFunction<...> -- use fun1<..>(...).name)MapEntryFeatureAssertionsSpec.kt from atrium-api-fluent-en_GB-common to atrium-api-infix-en_GB-commonKFunction<...> -- use fun1<..>(...).name)I'll work on this if you would like to take this issue over.Hi Rob, could you assign this to me?
Hi Rob, I haven't made as much progress on this one as I would have liked. I am having a lot of trouble with the MapEntryAssertionsSpec class. I have been reading about reflection inside of Kotlin. It is my understanding that the line "fun2(Expect
Your understanding is correct Expect<Map.Entry<String, Int>>::isKeyValue gets a function reference. Maybe the confusion comes from fun2? fun2 is a helper function to do two things, get the name of a function (out of the given KFunction) and use the function as such (KFunction as lambda). Further tips are given in the review
I am fairly stuck on this issue and won't have a lot of time in the next month to work on this so I believe it would be best if this was reassigned
No worries, I'll merge your PR into a different branch tomorrow and take over. Thanks for what is already done :)
Really appreciate all of the guidance sorry I couldn't be more help
Come back once you have more time again, your contribution is always welcome and I am happy to help out.
In case someone want to take over the work from @npswedberg base your PR on the branch #267-map-entry-new-infix-api
I'll take over
the branch #267-map-entry-new-infix-api is quite outdated, maybe it is easier to just have a look at it but start off with a new branch
Ok
implemented with a1617fb