Description
Changes proposed in this Pull Request
- Update the Scan main section to make it handle the states provided by the latest version of the API.
Implementation notes
I took the opportunity to fix snake case keys and string dates at the data-layer for Scan and Scan History endpoints. For this to work, I had to update the Threat type and the Scan type.
Testing instructions
Case 1: Threats + Scan error
- Select a site that has Jetpack Scan which has threats and the Scan is reporting an error (one can force this in the code or editing the ScanThreats component props)
- Verify you see the normal Threats state and there is card that notifies you that an error happened
Case 2: Scan unavailable
See 1151678672052943-as-1172213533219281.
Unfortunately, no screenshots were provided by the developer.