We're sorry but this page doesn't work properly without JavaScript enabled. Please enable it to continue.
Feedback

Better Kotlin Multiplatform architecture with Dependency Injection and KSP

Formal Metadata

Title
Better Kotlin Multiplatform architecture with Dependency Injection and KSP
Alternative Title
Toward better Kotlin Multiplatform architecture with Dependency Injection and KSP
Title of Series
Number of Parts
542
Author
License
CC Attribution 2.0 Belgium:
You are free to use, adapt and copy, distribute and transmit the work or content in adapted or unchanged form for any legal purpose as long as the work is attributed to the author in the manner specified by the author or licensor.
Identifiers
Publisher
Release Date
Language

Content Metadata

Subject Area
Genre
Abstract
Dependency Injection has become boring in Kotlin Multiplatform projects. Now compiler plugins can make the use of this pattern exciting again! Kotlin Symbol Processor (KSP) brings the fun back and helps us manage our dependencies with a nice fully typed API. Let's deep dive into it and see how it works. In this presentation we will talk about what makes Compiler plugins useful. How they help us build more reliable applications by reducing boilerplate and generating robust APIs. How we generate code and why can be confusing or misunderstanding. So, we will take Dependency Injection as an excuse for our Kotlin Symbol Processor tour. First of all, we will configure a new processor module. Then we will see how we can create our own Kotlin symbol processor to enhance our architecture by providing a fully typed Dependency Injection API.