airport

--airportv1.5.0

`airport -I` command parser

macOScommand

$ airport -I | jc-rs --airport

A real pair

From the reference corpus (osx-10.14.6/airport-I.json). The left pane is the input the fixture ships; the right pane is the corpus's expected JSON. CI compares jc-rs with it field by field under the published differential. Hover a value to see where it came from.

airport -Iosx-10.14.6

     agrCtlRSSI: -66
     agrExtRSSI: 0
    agrCtlNoise: -90
    agrExtNoise: 0
          state: running
        op mode: station 
     lastTxRate: 195
        maxRate: 867
lastAssocStatus: 0
    802.11 auth: open
      link auth: wpa2-psk
          BSSID: 3c:37:86:15:ad:f9
           SSID: SnazzleDazzle
            MCS: 0
        channel: 48,80

expected outputjson

{
  "agrctlrssi": -66,
  "agrextrssi": 0,
  "agrctlnoise": -90,
  "agrextnoise": 0,
  "state": "running",
  "op_mode": "station",
  "lasttxrate": 195,
  "maxrate": 867,
  "lastassocstatus": 0,
  "802_11_auth": "open",
  "link_auth": "wpa2-psk",
  "bssid": "3c:37:86:15:ad:f9",
  "ssid": "SnazzleDazzle",
  "mcs": 0,
  "channel": "48,80"
}

Fixture coverage

1/1oracle-valid pairs match under the published structural JSON comparison

Magic syntax

jc-rs airport -Ijc-rs runs the command itself and parses what it prints. Recognised for: `airport -I`

Source: crates/jc-rs-parsers/src/misc/airport.rs. jc-rs targets the schemas defined by the original Python tool. Fixture coverage above is the measured evidence for this parser; test the inputs your pipeline depends on. Compare