multiselect | jQuery multiselect plugin with two sides | Plugin library

There are a few bugs in your code preventing it from working.

Here is a working stackblitz: https://stackblitz.com/edit/angular-ivy-2zdvpu

The main problems are described bellow:

1. You must use the compareWith function on the mat-select-input in order to change its value using patchValue, as described here Angular patchValue of a mat-select component

HTML:

One solution would be to add a control for your options to the formGroup so that you can retrieve it from the formArray via index.

Add carPartSubCategoryOptions to both your createCat and initCat functions.

You can not use vuejs-datepicker in Vue3, you can try with vue3datepicker :

It looks like you have an older version of Node? https://github.com/nuxt/nuxt.js/issues/2385#issuecomment-358111543

Try to upgrade it to the latest LTS aka 14 and double-check that you got the latest version of Nuxt too.

You have to always use sorting with paging, even for the default case.

It is simpler to count distinct(name, value) pairs. Don't forget to sort them.

Better to use inner join here

As Angular docs says:

A common pattern in Angular is sharing data between a parent component and one or more child components. Implement this pattern with the @Input() and @Output() decorators.

Sending data to a child component

It is necessary to create a variable with @Input() decorator:

Here is a working stackblitz: https://stackblitz.com/edit/angular-13-starter-x-z434ak?file=src/app/app.component.ts

Issues boil down to the following:

1. Make sure you using a formGroup to wrap your whole form itself
2. Ensure that the compareWith function is comparing against the correct fields.

In the above I switched manufacturer to be the whole object, you would note however that there is a difference between the two objects it is comparing. I suspect this is due to differences between what you are actually setting as your source and the underlying representation of each item.

1. If you wanted to still just use the name directly then your compare with would look like so:

You seem to be using Windows cmd to run the command, and hence you are getting the error.

The command:

The answer is: Yes! The description in the documentation of Dropdown | PrimeVue is a bit confusing, at least for me. The problem is, that it isn´t enough to provide a v-model as I did with v-model="selectedFilter[index].pos", I also have to define optionValue and in my case optionValue="value", because the values in filterPositions have the key value.

Looks like, if this is set, PrimeVue´s Dropdown is able to check if the v-model matches the optionValue. If not, v-model would be compared to the whole filterPositions item. For example:

Without optionValue="value":