This is a public client ID for OAuth authorization purposes, but the value is currently hardcoded to a development ID, which obviously won't work for others. This value needs to sanely set by a "TASTYTERM_OAUTH_CLIENT_ID" environment variable somehow, because that's how the deploying organization will expect to set it when running the app via the official Docker image.

This is so they can be used in KNARTwork and other projects.

At present, the client provide read-only support. If and only if the app is (1) launched in SoF mode and (2) provide the appropriate OAuth scope/privilege, the client should support CRUD operations for all data objects.

Epic!

Currently using the old Http module. We need to upgrade as this is deprecated and may break in the future.

https://angular.io/tutorial/toh-pt6#get-heroes-with-httpclient

Expired tokens aren't currently handled. After application launch, we just assume that it's always valid. :). The code needs be refactored slightly to move the authentication code into a proper service, with events that trigger for expiry. There are existing examples on the web, if needed.

It's important to not hack this, because the code will need to be reused in other projects.

This borrows from a conceptual design of a prior work of mine. Will take an hour or so to explain the concept, and a little experimentation both to settle on the 3D library and figure out the best way to integrate it with Angular.

I previously went down a few paths, but everything always felt lame. The 2D graph navigation should be intuitive to use, interactive, and fast to load related resources.

As a user I'd like to get a permalink to the select code, so I can send a link to the same view to colleagues via email, chat apps, Word etc.

Webpack upgrade didn't work out of the box. Not sure what the deal is.