The issue was because we cache the value in the current composition, and
the next composition returns the cached value.
There weren't an issue if we just call one `stringResource` after
another because those are different compositions.
Fixes https://github.com/JetBrains/compose-multiplatform/issues/4325
Introduced a function to process and replace certain escaped symbols
like '\n', '\t', and '\uXXXX' in the strings extracted from compose
string resources.
There was a problem with an android publication. Android artifactId has
name "module_name"-"android" even though we explicitly renamed
artifactId inside the configureMavenPublication block. It means that
"components-ui-tooling-preview" android library rewrites
"components-resources" android library on the maven. Because they have
the same name "library-android".
* First pass at adding Xml parsing support to js platform
Likely still need to add tests and samples
* Add JS to Parser Node and Element converter
Mirrors native impl by returning empty strings when content is unavailable
Moves MalformedXMLException out of native code, useful for common case.
* Remove unneeded null checks in Parser
Last commit handled null management
* Add newlines for code linter
* Fix namespaceUri bug
Undo accidental capture of localName
Also remove unneeded null check
* Undo grade.properies change
Had to disable webpack version number property to run sample
* Clean up NodeImpl comments
Corrected description
* Make NodeList impl lazy
Generates only when needed, serves cache after
* Added animated image component
* Simplified network request
* Resource load is now done in the IO Dispatchers
* Renamed constant to express better its use
* Refactored animated image component to use the default Image component instead of creating our own component
* Added missing keys
* Created new module resources & adapted AnimatedImage to it