Tom Schönmann

Thanks for the work, would greatly appreciate if this PR could be merged soon! I'm currently using an intersection observer as workaround, but would be nice if we could use...

For anyone else coming across the same issue, you can actually use the Splide API for it. Here's a simple piece of code to determine what end of container should...

I can image that it might be enough to provide a selection between the `v1.1/v2` api surface to use in the CP (or via configuration). In code, a simple mapping...

Looking further into the issue, the **3rd party OAuth library** might also be the cause of failed requests here. The plugin currently uses the `OAuth1`-handler from `League`, but we might...

Thanks for the heads up, can you provide a (rough) timeline? It would help me estimate if we have to roll our own solution, or go with Verbb. Thanks!

Thanks for the update! Would it be possible to participate in a beta? I'll probably need an implementation end of January/start of February. Maybe I could meet the requirements with...

@engram-design Do you have any more information on this? Feedback would be much appreciated! Thanks!

Many thanks for taking a look @micheleriva! But I think there's a small confusion 😄: - my ticket is about **Next.js (React Framework using their app-router)** of version 14 -...

What worked for me was not using `'@orama/plugin-data-persistence/server'` but instead the (polymorphic?) client-JS import: `'@orama/plugin-data-persistence'` [link](https://docs.askorama.ai/open-source/plugins/plugin-data-persistence)