AM
JsonParametricSerializer -- 🎉🎉🎉
Size: a a a
2020 March 05
DZ
Аа, отделили, вот оно что. Спс
ТБ
это же что-то андроидное вроде
Не, это бекенд под jvm, просто мы ktor используем.
ТБ
Server admin tool?
там
там
R похоже просто имя диска, а не класс ресурсов андроид )Да, все так )
AN
@sandwwraith Вы https://github.com/Kotlin/kotlinx.serialization/issues/378 к релизу-то пофиксите? Это сейчас главная проблема.
VT
да, пофиксим
AN
да, пофиксим
🙏
AF
Всем привет. У меня кейс когда Flow эммиитит данные, и в одном из операторов происходит их сортировка на дефолтном диспатчере.
Не могу никак нормально придумать, как подменять компаратор если пользователь выбрал в UI новый тип сортировки.
Не могу никак нормально придумать, как подменять компаратор если пользователь выбрал в UI новый тип сортировки.
M
Hello everyone!
M
I have a situation on Enums
M
My question being:
QH
Hello everyone!
AL
Hello everyone!
Hi. Next time please compose your text as a single message. Thanks :)
M
Hi. Next time please compose your text as a single message. Thanks :)
Thank you, noted.
M
My question being:
So, what's the question?
M
Suppose I have two different enum classes that have the same number of fields as well as definitions:
E.g:
enum class EnumA {
Normal,
Abnormal
}
enum class EnumB {
Normal,
Abnormal
}
Is there a recommended way of having a single Enum class which holds the (Normal, Abnormal) fields, from which enum classes EnumA and EnumB can reference, instead of having a repetition of defining the same number of fields(order and names)?
E.g:
enum class EnumA {
Normal,
Abnormal
}
enum class EnumB {
Normal,
Abnormal
}
Is there a recommended way of having a single Enum class which holds the (Normal, Abnormal) fields, from which enum classes EnumA and EnumB can reference, instead of having a repetition of defining the same number of fields(order and names)?
AK
So what the problem to drop one of that enums?
AM
Из чейнджлога Detekt:
1.7.0 - Upcoming
Notable Changes
* The Gradle plugin should be on par with the CLI performance-wise
1.7.0 - Upcoming
Notable Changes
* The Gradle plugin should be on par with the CLI performance-wise
t
Suppose I have two different enum classes that have the same number of fields as well as definitions:
E.g:
enum class EnumA {
Normal,
Abnormal
}
enum class EnumB {
Normal,
Abnormal
}
Is there a recommended way of having a single Enum class which holds the (Normal, Abnormal) fields, from which enum classes EnumA and EnumB can reference, instead of having a repetition of defining the same number of fields(order and names)?
E.g:
enum class EnumA {
Normal,
Abnormal
}
enum class EnumB {
Normal,
Abnormal
}
Is there a recommended way of having a single Enum class which holds the (Normal, Abnormal) fields, from which enum classes EnumA and EnumB can reference, instead of having a repetition of defining the same number of fields(order and names)?
Have you tried Sealed classes?