Hi everyone! Does anyone know if <https://github.c...
# serializationm
Marc Dietrichstein
10/22/2019, 12:09 PMHi everyone! Does anyone know if https://github.com/Kotlin/kotlinx.serialization is the offical repository for this project? I'm trying to find out if using kotlinx.serialization is viable in the long term. We're stuck on kotlin 1.3.31 due to issues with kotlinx.serialiation in our multi-platform project and I have no idea if/when they will be resolved.
There are no answers in the github issue tracker for the problems that affect us. I was wondering if there is a better place to report issues since there is not much dev activity in the repository or issue tracker on github.
r
ribesg
10/22/2019, 1:07 PMWhat problems do you have? Staying behind on Kotlin version when using these kind of official but “Moving Fast” libs is dangerous
ribesg
10/22/2019, 1:11 PMTo answer your questions: 1) See topic 2) It’s basically the only way to go 3) Make sure your issues are real and there are no workaround available
m
Marc Dietrichstein
10/22/2019, 1:51 PMHey @ribesg
1) and 2): I thought so 🙂
3) An 'java.lang.IndexOutOfBoundsException' during compilation keeps us from using kotlin 1.3.50 (issues https://github.com/Kotlin/kotlinx.serialization/issues/527 and/or https://github.com/Kotlin/kotlinx.serialization/issues/563).
r
ribesg
10/22/2019, 2:04 PMI got this once I think and there’s a workaround
ribesg
10/22/2019, 2:04 PMJust don’t use typealias and put some TODO comment there pointing to the github issues
ribesg
10/22/2019, 2:05 PM(In my case I didn’t really need typealias)
ribesg
10/22/2019, 2:06 PMI also had an issue with a property initialized with other properties values. I replaced that property with a property without backing field
m
Marc Dietrichstein
10/22/2019, 2:23 PMRemoving the typealiases is sadly not an option. Our codebase is already quite big and uses them extensivley 😕
The second issue you've mentioned is new to me. I'll check if that's something we're doing as well. Thanks!
r
ribesg
10/22/2019, 2:53 PMWell the other option for typealiases is to actually dive into kotlinx.serialization, find the issue and contribute to it but... Good luck with that 🙂
m
Marc Dietrichstein
10/22/2019, 2:59 PMhehe yeah, that thought crossed my mind. But I have no idea how to set up a dev environment that would allow me to debug gradle, kotlin compiler plugins and konan.
Would be a fun weekend(s) project though 😉
s
sandwwraith
10/22/2019, 3:03 PMSorry about that, I'll take a look at that tickets again. It's really easy how they can slip out of mind...
👍 2
m
Marc Dietrichstein
10/22/2019, 3:12 PMNo worries. The project is already so useful that we enjoy using it even on
kotlin 1.3.31Marc Dietrichstein
10/22/2019, 3:13 PMIn connection with compiler/plugin issues in general, it would be helpful if there were a guide that describes how to debug such problems. One that explains how to setup gradle, kotlin, konan, kotlinx.serialization, etc. in such a way that allows us to give you more useful feedback (or even bugfixes)
Marc Dietrichstein
10/29/2019, 2:18 PMHey @sandwwraith! Have you had a chance to look at the issues?
s
sandwwraith
10/31/2019, 4:37 PMNot yet 😞 . But I don't think that one with typealiases would be hard to fix
l
louiscad
01/19/2020, 12:21 PMIt looks like it's been fixed in 1.3.60 judging from the GitHub issues. Can you confirm @Marc Dietrichstein?
m
Marc Dietrichstein
01/20/2020, 7:31 AMWorks like a charm 🙂 We were finally able to upgrade to 1.3.60. Thanks alot @louiscad
👌 1
5 Views