Skip to main content

How to catch event: re-initialise search in Algolia Instantsearch?

I am using Algolia and the Instantsearch library in a Vue project, to search for items. The user has the option to check each item (with a simple checkbox). Checking at least one item makes a toolbar visible, with a selection of actions to be applied on the selected batch of items in the search results. When an search result item is checked, it fires a Vue method that pushes the item to a Vuex array called "selectedItems". In order not to lose this selection with pagination, I have gone for the infinite hits widget. Thus all results remain on the same page. Until here things work fine. My problem is that when the user clicks on the cross in the searchbox to reinitialise the search, then the items are not checked anymore, but obviously they remain within the "selectedItems" array in Vuex. How can I capture the event of the search re-initialising? If I can catch this event, I can then empty the "selectedItems" array so that it remains in sync with the search results. I have only found this resource that presents events like click, conversion, view: https://www.algolia.com/doc/guides/building-search-ui/going-further/send-insights-events/js/ But nothing about other events like re-initialize search. Thanks for any help!

Via Active questions tagged javascript - Stack Overflow https://ift.tt/xcE6ZuR

Comments

Popular posts from this blog

How to show number of registered users in Laravel based on usertype?

i'm trying to display data from the database in the admin dashboard i used this: <?php use Illuminate\Support\Facades\DB; $users = DB::table('users')->count(); echo $users; ?> and i have successfully get the correct data from the database but what if i want to display a specific data for example in this user table there is "usertype" that specify if the user is normal user or admin i want to user the same code above but to display a specific usertype i tried this: <?php use Illuminate\Support\Facades\DB; $users = DB::table('users')->count()->WHERE usertype =admin; echo $users; ?> but it didn't work, what am i doing wrong? source https://stackoverflow.com/questions/68199726/how-to-show-number-of-registered-users-in-laravel-based-on-usertype

Why is my reports service not connecting?

I am trying to pull some data from a Postgres database using Node.js and node-postures but I can't figure out why my service isn't connecting. my routes/index.js file: const express = require('express'); const router = express.Router(); const ordersCountController = require('../controllers/ordersCountController'); const ordersController = require('../controllers/ordersController'); const weeklyReportsController = require('../controllers/weeklyReportsController'); router.get('/orders_count', ordersCountController); router.get('/orders', ordersController); router.get('/weekly_reports', weeklyReportsController); module.exports = router; My controllers/weeklyReportsController.js file: const weeklyReportsService = require('../services/weeklyReportsService'); const weeklyReportsController = async (req, res) => { try { const data = await weeklyReportsService; res.json({data}) console...

ValueError: X has 10 features, but LinearRegression is expecting 1 features as input

So, I am trying to predict the model but its throwing error like it has 10 features but it expacts only 1. So I am confused can anyone help me with it? more importantly its not working for me when my friend runs it. It works perfectly fine dose anyone know the reason about it? cv = KFold(n_splits = 10) all_loss = [] for i in range(9): # 1st for loop over polynomial orders poly_order = i X_train = make_polynomial(x, poly_order) loss_at_order = [] # initiate a set to collect loss for CV for train_index, test_index in cv.split(X_train): print('TRAIN:', train_index, 'TEST:', test_index) X_train_cv, X_test_cv = X_train[train_index], X_test[test_index] t_train_cv, t_test_cv = t[train_index], t[test_index] reg.fit(X_train_cv, t_train_cv) loss_at_order.append(np.mean((t_test_cv - reg.predict(X_test_cv))**2)) # collect loss at fold all_loss.append(np.mean(loss_at_order)) # collect loss at order plt.plot(np.log(al...