Hi! For Android is is fairly easy to communicate w...

# compose

[Joakim Forslund]

Hi! For Android is is fairly easy to communicate whichs strings we want to show to a user over a eventbus-like system, as we can simply send which resource id we want to show a user as an Int and also serialize this for logging reasons. For Compose Multiplatform and Compose Resources it is not as easy, while the StringResource can be sent over the bus we also want to be able to gracefully log this and and persist a specific latest error text triggered I've tried to write a KSerializer for StringResource but most of the content is internal and is not made to be instanceable or mappable. I preferably would not want to have to keep an interal mapping system to handle this. What are the options available to persist or easily map a StringResource currently?

[Mark Murphy]

we can simply send which resource id we want to show a user as an Int and also serialize this for logging reasons

Note that in Android, resource IDs can change per build. I would not persist resource ID values in any form (database, logging, whatever).

[Joakim Forslund]

Fair point