Repository navigation
refactor(APP-1339): Move the ChangeSettings action view from gov-ui-kit to the app - #1493
Merged
milosh86 merged 4 commits intoOct 15, 2026
Conversation
Signed-off-by: Milos Dzepina <milos@aragon.org>
|
🚀 Preview Deployment: View Here |
|
E2E results (preview) Smoke
|
Signed-off-by: Milos Dzepina <milos@aragon.org>
Signed-off-by: Milos Dzepina <milos@aragon.org>
… drop the kit's built-in action views (#1494) Signed-off-by: Milos Dzepina <milos@aragon.org>
5 of 14 tasks
This branch was successfully deployed
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Description
Moves the proposal detail view for plugin settings changes out of gov-ui-kit and into the app. Follows #1433 (WithdrawToken), #1489 (UpdateMetadata) and #1492 (TokenMint).
Unlike the previous migrations, the view cannot read the raw action: each plugin needs DAO data to build the settings rows (multisig the member count, token and lock-to-vote the plugin token, all of them translations). The plugins therefore keep their conversion, and only its output and view move to the app.
App
IProposalActionChangeSettingsin the governance domain (proposedSettings/existingSettingsas term/definition lists) with an app-only typeProposalActionType.CHANGE_SETTINGS = 'CHANGE_SETTINGS'. The backend never sends it, and its PascalCase types cannot collide with it.normalizeChangeSettingsActionnow return that type instead of the kit'sCHANGE_SETTINGS_MULTISIG/CHANGE_SETTINGS_TOKENVOTE. Their action types extend the app'sIProposalActioninstead of the kit type.ChangeSettingsActionDetailsinapps/app/src/actions/core/changeSettings/, registered forCHANGE_SETTINGS. It renders the same toggle and definition list as the kit view, and keeps the current side selected when its toggle is clicked again. Copy moved toapp.actions.core.changeSettingsActionDetails.*.gov-ui-kit (breaking, major changeset)
ProposalActionChangeSettings,IProposalActionChangeSettings/IProposalActionChangeSettingsProps,generateProposalActionChangeSettings,ProposalActionType.CHANGE_SETTINGS_MULTISIG/CHANGE_SETTINGS_TOKENVOTE,isChangeSettingsActionwith its branch inProposalActionsItemBasicView, and theproposalActionsChangeSettingsmodules copy.DefinitionListandIDefinitionSettingare still exported.ProposalActions.Rootstory now shows a remove-members action.Tests
normalizeChangeSettingsAction, which had none. They check the output type, that other action fields are kept, and what is passed toparseSettings: the existing settings, then the proposed settings merged over them, plus the member count (multisig) or plugin token (token, lock-to-vote).Changesets:
@aragon/gov-ui-kitmajor and@aragon/apppatch, one changeset per release scope.Type of Change
Developer Checklist:
Review Checklist: