refactor: device type registry system for future extensibility summary #172
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Changes
Device Type Registry (
types/device_type_registry.rs)DeviceTypeInfotrait for device type metadata (type codes, capabilities, connection types)OnceLockDeviceType Enhancements
supports_scanning()- query scan capabilityrequires_specific_object()- query if AP/target neededhas_global_enabled_state()- query radio control capabilityconnection_type_str()- get NM connection type stringto_code()- get raw type codeDisplaynow shows registry names forOther(_)variants (e.g.,Other(29)displays as "WireGuard")Settings Proxy Helpers
settings_proxy()andconnection_settings_proxy()helpersconnection_settings.rsandvpn.rsConnectionOptions
DefaultimplementationDeviceType::Other(_)variants now have proper names and capability queries via registry. Future device types can be added without API breakage.