app-router | Router for Web Components | Router library

This is the index.html file. By default, this page is rendered initially. Then I want to navigate to other pages. But that's not happening.

I'm trying to access an S/4HANA on Premise system via the Cloud Connector and SAP Cloud Platform connectivity service using the SAP Cloud SDK for JavaScript (version 1.5.0).

In detail, I have

• Cloud Connector
• connectivity service
• xsuaa service instance
• Application Router (app-router)
• destination
• destination service

which all work as expected. These preconditions are explained by different tutorials (https://blogs.sap.com/2019/04/02/a-do-it-yourself-at-home-guide-how-to-connect-a-node.js-app-on-sap-cloud-platform-for-the-cloud-foundry-to-an-s4hana-on-premise-system-securely-via-cloud-connector/, https://blogs.sap.com/2017/07/13/part-2-how-to-use-the-sap-cloud-platform-connectivity-and-the-cloud-connector-in-the-cloud-foundry-environment/).

With this setup I have no difficulties accessing an S/4HANA Cloud system. When using the SAP Cloud SDK for Java everything works as expected, i.e. I can access the on premise system. I have sufficient rights on the on premise system. Basic Authentication is used.

Example GET request for retrieving document info records using the SAP Cloud SDK JavaScript:

I'd like to scope a singleton to a route so that a new instance is created every time the user re-enters the route. I thought I could register an instance on the (automatically created) child container in the route view-model, but I get the error:

ERROR [app-router] ReferenceError: Cannot access 'SomeOtherClass' before initialization

How do I register a singleton within a route's container so that it is scoped only to that route?

My route VM looks like

I try to configure routing in angular 8.x application, with lazy loading and named outlets. I have the next configuration:

main-layout.html

I serve all types of containers (docker) behind a reverse proxy (traefik 2.0), like backend apps (nodejs) or frontend apps (vuejs). Actually, I am trying to serve a VueJS behind a path like https://localhost/my-app.

• Traefik redirecting /my-app to my vuejs container
• VueJS app working clean.
• VueJS app loads resources with relative paths like .

• VueJS app not working because is not getting resources properly.
• I am getting only index.html (root page of VueJS) behind https://localhost/my-app
• My browser is trying to get relative resources on https://localhost/css/app.css instead of https://localhost/my-app/css/app.css Have you an idea how to serve VueJS with relative resources behind my /my-app redirection

See configuration files below.

I'm using React Router 4 in a TypeScript app where I have a React.Component that's used within a React.FunctionalComponent. I need to be able to navigate programmatically to a particular route from within the React.Component, but I can't seem to figure out how to pass the router down to the child component so that I can call this.props.history.push(). What complicates matters is that I'm using TypeScript, too.

Here's a code sandbox with a working demo of my component layout: https://codesandbox.io/s/react-programmatic-routing-xebpg

And now, the components:

app.tsx:

I'm learning React-Router with typescript and coming into a typing issue.

I was running on an older version of react and react-router. I've updated to the latest builds with yarn.

I am creating a portfolio website, where in this design, I have a background for the entire website that will stay fixed as content scrolls over it. The Navbar is also fixed, and has the content scrolling under it.

This design looks cool, and wasn't too hard to put together, but I am having a little bit of trouble incorporating React Routing into this mix.

From what I gathered, the tutorials say to create a App-Router component, which basically looks like their way of saying "Navbar". So I did that and got my Navbar to route to my Home, and About Me component pages. However, since my Navbar is fixed, all the pages refuse to scroll, which means they are being included inside the Navbar component. This is the opposite of what I want to have happen.

My Ideal setup would be to have the Navigation Bar (It's own component) send a routing request to a Routing component, which will then render that component (bellow the Navbar, still contained within the app container which contains the background).

Here is some psuedo code of my structure so far (the bad code):

App.js

I'm trying to compare defined role (in my app.ts) and revived role from WebServer. But when I'm not logged I have problem with compare values:

This is what I'm doing: