Closed Rigo-m closed 5 months ago
Hey @Rigo-m
Thanks for this change! I will take a look at it in the upcoming days
hi @Baroshem! Any news?
Hey folks,
Sorry for no contact. I have been recently busy with other modules.
I will set it as a priority to handle this once I will be back from vacation 1st December.
I will review this and possibly merge as it is a good example :)
Just a quick follow-up with some ideas:
Hey @Rigo-m
Sorry for long time waiting but I was away for almost two last weeks.
I am up for showing your GitHub repo as the example in the documentation if you are ok with that but we can also work on implementing a new version of the module with a feature that could make it simplier for users to work with it :)
I think it would be cool to provide it via the module, so that users are encouraged to use the solution and find issues (so that its eventual fix can benefit everyone)
Up to you if you want to provide the components and/or point to this issue in the docs :) I think the previous solution was bad in many ways that's why i opened this.
As per the point number 2, instantsearch for vue really sucks, if by any means my sorry ass starts to move and I start to do some open source work I really want to rewrite algolia's library for vue from the ground up :D
So my recommendation will be to add the link right now and if you like and have time, I would really appreciate if you could create a Proof of Concept PR with your solution.
I can add the link to the docs in the upcoming days if you agree :)
Then we could decide how to make it work the best way for the users.
Thanks for all the ideas and dedication for making the module better! 💚
@Baroshem closing this. The proposed SSR implementation had many problems that we encountered in real life applications and a bad DX, started working on something better :)
https://github.com/atoms-studio/nuxt-swiftsearch for everyone stumbling across this issue
Take a look at this. It's a different (and imho better) way to implement SSR Instantsearch on algolia. It does not require you to write a carbon copy of the render function of the component, and it's more understandable how it works.
@Baroshem let me know what you think