ink-react | Declarative email templates using react.js and ink.css | Frontend Framework library

If you are not sure that using onClick on that link is a reliable way, you can create a wrapper component around the link and put the onClick on it. When you click, the click event will bubble up until your wrapper component so you can handle it. That way your wrapper element is responsible for handling this.

If you don't want to add a wrapper element, you could add the onMouseUp to the Link component and call openSB(!open); from there, that way onClick is untouched.

You can use your ajax call inside the built-in ajax parameter when initializing a datatable, and send the data to datatable's callback method:

I would suggest using redux for retrieving the data. When you navigate to product route you can get the product details by dispatching some action.

You will need to store the columns which already exist in a key-value array. It would start as an empty array, then you will loop through your items, check whether their value exists in the key-value array. If so, add the new value to the already created value, which should be an array. When you have finished this, you will have a key-value array, each key representing a column and each value representing the array of items in the column. You will have two nested loops. The outer loop will loop the columns. The inner loop will loop the values. And you will need to define your HTML to be displayed according to your needs.

Do some changes

View

Add enctype="multipart/form-data" in the

It's clear that you're trying to run before you can walk here.

Firstly, you should concentrate on getting a simple list view to work, without getting confused about the additional complexity involved in displaying a list in a form view. So, make your view inherit from ListView, and remove all the methods. Then fix your template, so that it iterates over stock_list or object_list rather than just stock.

Secondly, once you've got that working, you could try to integrate it with a form. When you do that, learn what methods to override. get_queryset must return a queryset, it should not render a template. In any case, you should almost never need to render a template manually in a class-based view, because the existing logic will do that for you. And if you want to add a queryset to the template context in a create view, for example, you should be overriding get_context_data; which needs to return a dictionary.

Thirdly, if at some point you do need to render a template manually, read the documentation to learn the order of parameters to render: it is request, template_name, context, not as you have it.

There are two things i am noticing:

1. Instead use .closest() against .parent() multiple times.
2. Do not set the attribute in the if condition, instead of .attr() use .prop().

You can change to this

There are a couple of problems here:

• You are cloning elements and then trying to access them via the same ID (you should use class)
• Your functions don't target just clicked element but any element with the selector.
• You are cloning elements so you need bind the click event to a non-cloned element: e.g. via $(document).on

I've updated some of your code to demonstrate what I'm talking about. In the html, I've added classes in the trigger2 and hidden_fields2 elements and display:none style to the hidden fields so they are hidden by default.:

Okay, so I finally figured it out. I have to trigger the onchange event manually of each input with jQuery's .change() so the ajax gets executed and JSF recognizes the dynamic change of the values.