fix: map fourteen response fields the API returns

[danielabbatt]

Why this exists

#413 was merged into its base branch fix/map-observed-scalar-fields rather than into main, and #412 had already merged to main a minute earlier — so the nested-object work never reached main. This is that commit cherry-picked onto current main, with the changelog reworked.

What

Adds the seven nested response objects from the same unmapped-member export as #412. Callers who set JsonMissingMemberHandling.ThrowOnError were getting a failed deserialization rather than an ignored field.

Field	Type	Access	Source
TwoPointFourGhzSettings.Dot11ax	TwoPointFourGhzSettingsDot11ax?	ReadWrite	v1.74.0 spec, request + response
FiveGhzSettings.Dot11ax	FiveGhzSettingsDot11ax?	ReadWrite	v1.74.0 spec, request + response
SwitchPort.PerpetualPoe	SwitchPortPerpetualPoe?	ReadUpdate	v1.74.0 spec, request + response
SwitchPort.FastPoe	SwitchPortFastPoe?	ReadUpdate	v1.74.0 spec, request + response
NetworkApplianceSsidRadiusServer.Radsec	NetworkApplianceSsidRadiusServerRadsec?	Read	Observed only
Admin.OtherOrganizationAccounts	AdminOtherOrganizationAccounts?	Read	Observed only
VpnBgp.Ipv6	VpnBgpIpv6?	Read	Observed only
VpnBgp.TunnelDownTermination	VpnBgpTunnelDownTermination?	Read	Observed only

Ten new classes back them, each named after its owner in line with the existing SwitchPortDot3az / ConfigTemplateSwitchProfilePortDot3az split rather than sharing one enabled-only type.

The spec also marks axEnabled deprecated in favour of dot11ax.enabled on both bands, which the XML docs now say. No behaviour change — AxEnabled stays in place.

Changelog

The 1.70.135 and 1.70.136 sections are merged into a single 1.70.138 section covering all fourteen fields. The old labels no longer matched anything buildable: merge commits pushed main to 1.70.136 while its section said 1.70.135. 1.70.138 is what main will build as once this merges with a merge commit (this commit alone is 1.70.137).

Verification

dotnet build Meraki.Api.slnx -c Debug      Build succeeded, 0 Error(s), 6 pre-existing CS0618 warnings
Meraki.Api.Test (Data namespace)           Total: 14, Errors: 0, Failed: 0, Skipped: 0
Meraki.Api.Test (Workflows)                Total: 12, Errors: 0, Failed: 0, Skipped: 0

Clean cherry-pick, no conflicts. Every source diff is pure addition (0 deletions), so per-file BOMs are untouched; the CHANGELOG diff is the section merge, kept CRLF.

Cleanup

fix/map-observed-scalar-fields still holds #413's merge commit and can be deleted once this lands.

Notes

• SixGhzSettings has no dot11ax in the spec or in any observed response, so it is untouched.
• SwitchPort.ActiveVlans is mapped ReadUpdate while the config-template equivalent added in fix: map seven scalar response fields the API returns #412 is Read. Neither is in the spec; still worth a follow-up decision.

[codacy-production]

Not up to standards ⛔

🔴 Issues 1 medium

Alerts:
⚠ 1 issue (≤ 0 issues of at least minor severity)

Results:
1 new issue

Category	Results
Complexity	1 medium

View in Codacy

🟢 Metrics 8 complexity

Metric	Results
Complexity	8

View in Codacy

AI Reviewer: run a review on demand. To trigger the first review automatically, go to your organization or repository integration settings. AI can make mistakes. Always validate suggestions.

_{TIP This summary will be updated as you push new changes.}