dzikoysk

Class is a Type, but Type is not a Class so it makes handling worse for adapters as you could specify non serializable components. The only benefit of using `Type`...

I've made a prototype of this feature in: * https://github.com/javalin/javalin/pull/1657 Like I said, it's not that beauty because we've made handling experience a little bit worse due to casts &...

Not sure, as we were talking about those route listeners too. I think this particular issue is resolved and if we'll go back to those listeners topic, we'll create a...

None of the above examples fully work for me with **Gridsome** stack, but I've mixed them and here is a combination that pretty much works in every env I've tested:...

@anuraghazra some kind of lightweight cache could be a solution 🤔

Yup, we use these to properly display badges on GitHub in README etc.: * [MavenLatestApiEndpoints#L156](https://github.com/dzikoysk/reposilite/blob/aadad3e02ef004d06e3fd782b9d87c59732b0405/reposilite-backend/src/main/kotlin/com/reposilite/maven/infrastructure/MavenLatestApiEndpoints.kt#L156-L158)

I wonder if we want to keep simple statistics in Reposilite or we should fully move to external service 🤔

I think that when we'll have stable 3.x we could invest some time to write benchmarks. A few notes to the proposed scenarios: * Reposilite does not use cache, so...

> Performance benchmarks should be used to show users whether or not this tool is appropriate for them I mean, the result might be different, because there is e.g. disk...

Results could be summarized in guide: * https://github.com/dzikoysk/reposilite/blob/main/reposilite-site/data/guides/introduction/comparison.md