nickrobison / iot-lis Goto Github PK

Our OAuth logout flow (added with #18) removes the user token, but leaves it attached to the application settings page. That's annoying and incorrect.

Let's see if we can get some Okta integration working.

Github would be nice as well.

Right now, we only support unauthenticated connects to Simple Report, which is not good.

Fortunately, we won the war against late initialization with the SRBackend, so it should be as simple as injecting the Okta manager into the backend and intercepting requests.

The text on my blue buttons is driving me nuts. I think I need an alignment guide so I can center the text with the activity indicator being offset.

Now that we're all in on SimpleReport, we should remove the old PatientEntity.

We're not handling our Bluetooth connections correctly. We're only receiving a single packet and then returning. That's not how things actually work.

The solution is probably to make each BluetoothDevice the appropriate delegate, where we can then store some state.

We need to link the device ID to the result so we can keep the provenance chain intact.

This will be kind of interesting as it's possible for a single Bluetooth Gateway to have multiple devices attached.

When the application comes in from the backend, it should rescan and re-connect to devices.
But it doesn't.

It would be nice to have support for setting timers on each order to indicate when they're ready to be read.

There are some times when on first use, the SRBackend class will crash due to no network connection.

That seems odd, but I think we have two solutions.

1. Figure out why things are failing, when they shouldn't.
2. Try to catch the exception and retry it.

Let's do this for real.

When a result comes in for an order that doesn't exist, we should create one and then indicate that it's not linked to any patient.

The logout button in the settings page (as part of #18) is not aligned correctly. Looks like another use of alignment guides, like in #19.

Right now, the list of results returns the same date for every entry.
This is because the Swift iso date parser doesn't seem to be able to actually parse dates. Even if we generate a date string directly from a date object, it won't parse back.

Ugh, ugh, ugh.