Templater | A template plugin | Plugin library

When you want to redirect to a GET after a POST, the best practice is to redirect with a 303 status code, so just update your code to:

I was able to track down the source of the issue, and fix it. Sounds weird, but document.body.onmousedown and document.body.onmouseup were creating the issue.
Replacing them with addEventListener seems to fix it.

I also removed some repeated code (in slider's input listener), by making maximum use of createGrid() function.

You'll have to force cell.style.opacity to be a Number before doing addition on it; the += isn't working:

cell.style.opacity = Number(cell.style.opacity) + 0.1;

You can add an extra variable usersWithAGroup that memorize all the users actually assigned to a group :

Here:

When an expression fails to evaluate, Argo Workflows simply does not substitute the expression with its evaluated value. Argo Workflows passes the expression as if it were the parameter.

{{=}} "expression tag templates" in Argo Workflows must be written according to the expr language spec.

In simple tag templates, Argo Workflows itself does the interpreting. So hyphens in parameter names are allowed. For example, value: "{{inputs.parameters.what-it-is}}" is evaluated by Argo Workflows to be value: "over 9000!".

But in expression tag templates, expr interprets hyphens as minus operators. So value: "{{=inputs.parameters.what-it-is}}" looks like a really weird mathematical expression, fails, and isn't substituted. The workaround is to use ['what-it-is'] to access the appropriate map item.

My guess is that your expression is failing, Argo Workflows is passing the expression to dev-outputs-wft un-replaced, and whatever shell script is receiving that parameter is breaking.

If I'm right, the fix is easy:

DAG and steps templates do not automatically produce their child templates' outputs, even if there is only one child template.

For example, the no-parameters template here does not produce an output, even though it invokes a template which does have an output.

Because you are assigning instance to null. You should initialize the property by defining it first. On row your trying to access merchant_name but it may never be there or have anything.

Quick and easy fix could be to define what dataBK has. dataBK: any[] = []; If we don't care what it has or data type may change we can just use any.

Proper way would to create an interface. What dataBK holds? An array of Rows. Okay - what kind of Rows? We include merchant_name, account_number... in row objects. Then we always know, that dataBK will hold an array or Row objects. And we have defined, that Row object will have such properties to be accessed. Leaving in the ? as I can't be 100% sure they will be there to be accessed, maybe you do - in case you can remove the questions marks.

The rendered view and its children are only accessible when the template is rendered in the ViewContainerRef, so right here.

The rendered view cannot be obtained when usin ngTemplateOutlet, so i think your best bet is to copy the code and modify it to fit your requirements.