Mark Stacey 88ae10418b Expand usage of getProviderConfig selector (#18906) ... The `getProviderConfig` selector is now used anywhere the `provider` state was previously referenced directly. This was done to simplify renaming this state from `provider` to `providerConfig` in a later PR. Note that there are many opportunities left to use more-specific selectors (e.g. `getChainId()` over `getProviderConfig().chainId`), but that was intentionally omitted from this PR to reduce the size. I started going down this path and it quickly exploded in scope. Relates to #18902		2023-05-02 10:06:24 -02:30
..
advanced-tab	feat: add yaml feature management (#18125)	2023-04-25 16:32:51 +02:00
alerts-tab
contact-list-tab	Expand usage of getProviderConfig selector (#18906)	2023-05-02 10:06:24 -02:30
experimental-tab	feat: add yaml feature management (#18125)	2023-04-25 16:32:51 +02:00
info-tab	feat: add yaml feature management (#18125)	2023-04-25 16:32:51 +02:00
networks-tab	Refactor provider config selector (#18905)	2023-05-01 21:04:43 -02:30
security-tab
settings-search	feat: add yaml feature management (#18125)	2023-04-25 16:32:51 +02:00
settings-search-list	update icons to ts enum version (#18698)	2023-04-24 09:19:19 -05:00
settings-tab	Update settings-tab.component.js (#18753)	2023-04-25 08:27:19 -05:00
snaps	Update Button prop name type to variant (#18774)	2023-04-26 11:17:25 -05:00
index.js
index.scss	feat: add yaml feature management (#18125)	2023-04-25 16:32:51 +02:00
settings.component.js	feat: add yaml feature management (#18125)	2023-04-25 16:32:51 +02:00
settings.container.js
settings.stories.js
settings.test.js