diary | Web application for personal user diaries | Encryption library

You can only use an ID once on a page (must be unique), so having two divs with id="myModal" will not work. Fortunately you don't need those IDs, it's easy to get the "next" element of the button that was clicked, which happens to be the modal you want to open.

STRSQL doesn't have a version..

Or rather it's simply an optionally installed piece of the OS. Note that the DB itself is part of the OS also.

You need to determine the OS version you're running. Instead of running STRSQL at the command line try on of these:

• DSPDTAARA DTAARA(QSS1MRI)
• DSPPTF
• GO LICPGM -> Option '10'

Also, your VER command entry output is not from IBM i (aka AS/400)

The problem is, you are trying to display another UIAlertController on the currently presented UIAlertController.

You are presenting your UIAlertController twice.

Remove the line present(alert, animated: true, completion: nil) under let alert = ....

You're using the includes method which only returns the boolean. If it's matched, even got 4 matches, the number only will be increased by 1 for each loop.

This is another way to achieve that by using filter.

I'd like to thank S. Elliott Johnson for the solution I'll post below to anyone running into the same issue in the future:

This sounds like intended behavior. Your server routes and your React Router routes SHOULD NOT conflict.

React Router isn't actually "routing" anywhere from a HTTP sense -- it's just rendering different JavaScript/HTML and storing its "location" in the URL.

When running a React app, the React app is typically only served from the root of your website (or some other "root", like mydomain.com/app). When you make a HTTP GET request to that route, the backend server sends all of the JavaScript, HTML, and CSS necessary to bootstrap your React app. Clicking around using React Router simply causes your React code to run on the client.

When you actually reload the page, your browser, as you know, makes a GET request back to the server for that route, so you just get whatever your server sends. Let's use a few examples where you have a React app that's served from my domain.com.

Example 1:

• User makes a browser GET request to mydomain.com. They receive the React app back

• User navigates to /auth/login - no HTTP requests, React simply running code

• User navigates to /me to view their account -- again, same

• User reloads the page using the browser - a HTTP GET request is sent to the backend, and they'll receive whatever the backend sends back -- whether that's JSON or something else

You really have two options here:

1. Redirect all HTTP requests to root, meaning /, /something and /anything will serve /. Then host your API on another subdomain, like api.mydomain.com

2. Choose a route to serve your API from, like mydomain.com/api. Forward all requests from any route EXCEPT /api and it's subroutes to the root.

What I ended up doing was option 2:

Renamed my API routes prepending /api to all of them on server.js. Then I renamed all API calls on React accordingly. That code excerpt

Layout should render an Outlet for the children Routes to be rendered into.

It appears to be some sort of Angular application, which means that the value is rendered on the client side. BeautifulSoup probably retreives the html from the server, which includes the angular javascript without it being executed (since that is done at the client).

You could use a headless browser to load the data for you and scrape the values from there.