1.8.0

What's Changed

• feat(non-compose-accessors): add non compose accessors by @humblerookie in #40
• Use default language strings in the XML Processor if a translation is missing by @prof18 in #45
• Update to Kotlin 2.2.21 by @rsicarelli in #53
• Publish to Sonatype Central Portal by @Goooler in #52

New Contributors

• @humblerookie made their first contribution in #40
• @rsicarelli made their first contribution in #53
• @Goooler made their first contribution in #52

Full Changelog: 1.7.0...1.8.0

1.7.0

What's Changed

• Add wasmJS support | Update Kotlin and Compose by @skaldebane in #43
• iOS project sample with Xcodegen by @DevSrSouza in #44
• Add option on the xml processor to avoid creating compose accessors by @prof18 in #46

New Contributors

• @skaldebane made their first contribution in #43
• @prof18 made their first contribution in #46

Full Changelog: 1.6.2...1.7.0

1.6.2-1.8.20

Same as 1.6.2 but compatible with Kotlin 1.8.20.

1.6.2

• Set jvmTarget to Java 8 to make compatible with more projects (#28 by @DevSrSouza)

1.6.1

• Set jvmTarget to Java 17 (#26)

1.6.0

• Decoupled Lyricist API from Compose, it was moved to lyricist-core module
  • It is now possible to integrate with any UI Toolkit on supported platforms (docs)
• Added option to generate strings helper property (docs)
• Fixed "Strings for language tag not found" (#10)

1.5.0

• Make Lyricist class @Immutable (Based on discussion of PR #13)
• Generate interface (instead of data class) for strings migrated from XML (Based on discussion of PR #22)
• Fix issue #17: String resource references are not resolved (PR #24 by @devnatan)
• Update dependencies
  • Kotlin 1.9.10
  • Compose Multiplatform 1.5.3
  • Gradle 8.2.1
  • And others

1.4.2

• Better handling for multiple rounds of KSP generation to fix issues with multiple KSP plugins.

1.4.1

• Fix recompose whole app after change languageTag (#9) by @phucynwa
• Fix code generation for module that uses Explicit API

1.4.0

• New Module lyricist-core: With this module, now you can define your strings and properties in common code but only generate code for android target. This will allow sharing strings with iOS without requiring the Compose dependency. In the future, we should also support on Pure iOS (without Compose) system selected language support.