Let's also add this prop to the `InterfaceLicense` as `Array <LicenseHistoryItem>`. Here we can instantiate the default as `[]`. Avoiding null for array types is generally easier to work with - jus...
I think we can afford to be a bit more conservative here with our time window logic. BETWEEN is inclusive of both its beginning and end values, which makes it very easy to over- or under-report tra...
- needs design, frontend, updates backend record
- all privileges lost when new HS selected--warning message?
- can only switch once new HS has added the correct/updated license
### Requirements List
-
### Description List
-
### Testing List
- `yarn test:unit:all` should run without errors or warnings
- `yarn serve` should run without errors or warnings
- `yarn ...
I will be writing up a document of estimations for the following:
1. Monthly reports
2. Annual Reports
3. Custom range reporting through the application, with the following features/constraints
...
In the event that:
1) A privilege purchase transaction fails on the back-end,
2) The back-end attempts to roll back the transaction to get the practitioner's data into a consistent state, and
3) Ev...
We have written up the following design document capturing the various options (must have permission to view): https://docs.google.com/document/d/1qwb0dGWDamGDXsOGCHWp0yokEtL4vb2XJnklwJf6vLQ/edit?u...
@jusdino Looks good- do we need to handle the case where a field is _added_? Naively, I wonder if it would work to just do:
```python
updated_values = {key: value for key, value in new_lice...
I did not handle the case where a key is _removed_ in a new license in the first pass. I've updated this logic (and the API) to include a `removedValues` field to represent fields removed in an upd...
the public can look up a licensee by name, state, or license number and view their active and past privileges, purchase and expiration dates, and if any of those licenses have discipline