Commit 03b7a66
fix: handle absent tls/http fields in connectivity response (NON_NULL Jackson)
SpringWebConfig configures Jackson with NON_NULL inclusion, so null values
are omitted from the JSON response. ConnectivityController sets tls=null for
HTTP providers and when TCP fails, but those null values are stripped before
reaching the browser. The frontend received tls=undefined, and the strict
null check (=== null) fell through to tls.status, crashing with TypeError.
- ProviderConnectivity: mark tls and http as optional (| undefined) in api.ts
- ConnectivityRow: use == null (covers both null and undefined) for tlsOk
- TlsBadge / HttpBadge: accept undefined in prop type, use == null guard
Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>1 parent a34c56f commit 03b7a66
2 files changed
Lines changed: 7 additions & 7 deletions
| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
| |||
330 | 330 | | |
331 | 331 | | |
332 | 332 | | |
333 | | - | |
334 | | - | |
| 333 | + | |
| 334 | + | |
335 | 335 | | |
336 | 336 | | |
337 | 337 | | |
| |||
| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
| |||
30 | 30 | | |
31 | 31 | | |
32 | 32 | | |
33 | | - | |
34 | | - | |
| 33 | + | |
| 34 | + | |
35 | 35 | | |
36 | 36 | | |
37 | 37 | | |
| |||
44 | 44 | | |
45 | 45 | | |
46 | 46 | | |
47 | | - | |
48 | | - | |
| 47 | + | |
| 48 | + | |
49 | 49 | | |
50 | 50 | | |
51 | 51 | | |
| |||
117 | 117 | | |
118 | 118 | | |
119 | 119 | | |
120 | | - | |
| 120 | + | |
121 | 121 | | |
122 | 122 | | |
123 | 123 | | |
| |||
0 commit comments