portal-web | Portal of KuChain.network | Portal library

If you want to preserve the requested path, you need to remove the nginx.ingress.kubernetes.io/rewrite-target: /$2 annotation.

As per Nginx Ingress Rewrite:

In this ingress definition, any characters captured by (.*) will be assigned to the placeholder $2, which is then used as a parameter in the rewrite-target annotation.

i.e., the annotation is redirecting http://testapp/testapp-web-dev/manifest.json to http://testapp/manifest.json.

When you build in prod mode, angular tries to extract licenses from the 3rd party libs that you use into a 3rdpartylicenses.txt file. For that, it needs looking at package.json files.

Since you put your handontable package manually in your node_modules, it's missing package.json.

What you should really do is install handontable with npm (specify the version if needed)

To establish the hierarchy you need two things:

1) The router outlet in the parent component (which it sounds like you have).

2) The children property (when the routes are defined in the module) or loadChildren property (when the routes are defined in a separate module) for the parent route to let the router know which routes are the child routes.

ApplicationTabContainerComponent is missing the children or loadChildren route property. Otherwise there is nothing to tie the routes defined in Applications module to that route.

It's a bit challenging to get the syntax just right without having the code ... but it will look something like this:

You should use a WSDL to php generator that generates the PHP SDK in order to easeily consume the SOAP WS.

Take a look to the PackageGenerator project. It generates the struct classes used to contruct the request and the services classes to send the request.

The response handling is then easier as you only deal with known object classes generated by the generator, good luck,

As #assign creates/writes a variable in the namespace of the current template, while #list creates a variable in the scope of the loop (a more specific, narrower scope), that statement copies entity from the loop scope to the wider template namespace scope. If it's really needed in that template, I don't know; look for references to entry in that (or an #include/#imported-d) template that is outside the #list. It's not needed in the part quoted.

You can't just copy a bunch of non-Angular files and turn them into an Angular project.

The best route would be to start scaffolding the desired components/routing for your app and then copy the template code into the components by hand. This isn't really something you can automate, and how you decide to break the template into components will be a design decision you have to make. It's less a matter of adding the template to your project then rebuilding the template in Angular.

As far as basic code goes, just add whatever Javascript/CSS dependencies the template requires into Angular (either in index.html or using Angular CLI's script option). Just look up how to add Bootstrap 4 into an Angular Starter or CLI app and that should get you started.

Additionally, be aware that adding JQuery heavy interface elements to an Angular project isn't usually desirable since you are essentially using two orthogonal DOM manipulation systems. I'm not saying don't do it, but you may find that elements in the template don't play nice when you try to bind them or interact with them through Angular's DOM manipulation.

Use $("svg text") to select the text you are clicking on inside your svg.

Then use $(this).text() to get the text