mirror of
https://github.com/vitorpamplona/amethyst.git
synced 2026-08-09 16:14:40 +00:00
m
67edb32fa7
Two NamecoinSettings classes had drifted: - commons (used by Desktop): only enabled + customServers - amethyst service.namecoin (used by Android): full schema with backend, namecoinCoreRpc, fallbackToCustomElectrumx, fallbackToDefaultElectrumx This left Desktop unable to persist any of the Namecoin Core RPC or fallback-policy state introduced in the Android settings UI. Promote the rich Android version into commons as the single source of truth and delete the Android duplicate. - Move the rich schema (backend, namecoinCoreRpc, fallback toggles, hasUsableCoreRpc, toFallbackPolicy) into the commons NamecoinSettings. - Delete amethyst/service/namecoin/NamecoinSettings.kt and its test. - Repoint the two Android imports (NamecoinSharedPreferences, NamecoinSettingsSection) at the commons class. No behaviour change on Android. - Fold the Android-only backend/RPC/fallback test cases into the commons NamecoinSettingsTest so the shared schema stays covered. Desktop persistence (DesktopNamecoinPreferences) still only reads/writes enabled + customServers; the extra commons fields fall back to defaults on the existing Desktop store. Wiring those new fields into Desktop is the next change.