postAd | Google Keep-like ads wall | Frontend Framework library

You don't need js or vue to achieve it. You can utilize required attribute and :invalid pseudo class to control the styling.

You just have to use your "model" variable and then "schema_third.fields" and loop inside.

Once you loop, you can check if that model key, is set in the "model" object. If not set, then add the class "error-field" in each field's styleClasses. And do vice versa to remove that class, if the value is set.

Here is the code that you need to add to your checkForm function:

This is how livewire works. whenever you are changing anything / firing any event. the component will refresh. As far as I learned livewire, there is no way to stop it unless you are putting die() isnide showPOstAddedMessage function, which will be a very wierd way to solve it.

Make a seperate function this.handleClickButton and use it for New and Used buttons. instead this.handleChange

The problem you are having is that when the form is posted, ASP.NET will bind the posted data to your model, but only input values within the form are posted. The reason your SelectListItem has null Text and Value properties is because these values are not being posted in the form. The form would need to contain an input (such as a hidden input) for @Model.Features[i].Text and another for @Model.Features[i].Value for these to be bound back to the SelectListItem during model binding because it is the input's name that binds it to a model property. But keep in mind, receiving these from even hidden inputs would enable a user to change them to any value they want so you would need to validate on the server side that they are 1) valid values and 2) allowed to be selected.

Given that fact, I find it makes more sense to simply reload the list of available options, in your case Features, in your HttpPost action, then update that rebuilt list with the user's submitted selections.

Now the only problem left is you're not even getting Selected set to true. This is again, because it's based on the input's (the checkbox's) value. asp-for="@Model.Features[i].Selected" will give the checkbox the name it needs to bind back to that property, and will bind its value attribute to the value of Selected. However, you then also define your own value attribute as value="@Model.Features[i].Text" which overrides the one that would've been generated by the asp-for helper. So when your form is submitted, the model binder tries to bind "Camera" to the boolean Selected property which can't be done so it just gets it's default false value. Generally, a SelectListItem is used for a dropdown () input. There's no reason you can't use it for this purpose, but you could also just use your own model type for the checkboxes.

To have the slider fixed at the bottom add an ion-footer as shown in pseudo code below:

Before componentDidMount:

const that = this;

Then call later:

that.setState();

Read up on JavaScript “this” for an enlightened weekend. “You don’t know JavaScript yet” is an excellent read.

Also read up on react hooks.

seems like somewhere in your code you are trying to get some document from db with mongoose model but passing wrong argument. instead of valid mongo ObjectId value "addpost" is passed

The property will need to be repopulated on Post as well

Create a common function to get the data