<@U5P6T8EAJ> you could also use the decorator patt...

# announcements

[Andreas Sinz]

@mplacona you could also use the decorator pattern to cache data. have a common interface and create one implementation that fetches the data and another one that just caches the data:

interface FooTags {
    fun getTags(): Map<String, Int>
}

class FooTagsRetriever : FooTags {
    override fun getTags(): Map<String, Int> {
        //Get Tags via HTTP
    }
}

class FooTagsCache(private val retriever: FooTags): FooTags {
    private lateinit var tagCache: Map<String, Int>

    override fun getTags(): Map<String, Int> {
        If(!::tagCache.isInitialized) {
            tagCache = retriever.getTags())
        }
        
       return tagCache
}

Then you have transparent caching and can easily test every part in isolation

[mplacona]

That's awesome! Thank you!

[mplacona]

wait.. what does !:: do? I get "!" is NOT, but what does the :: after that do?

[Andreas Sinz]

@mplacona it gets a reference to the tagCache-property: https://kotlinlang.org/docs/reference/reflection.html#property-references

[mplacona]

TIL! Thanks again