# Handle new profile form in migrate_settings and migrate_language_setting \(\#53681\) · gitcafe/zed

[View on GitCafe](https://git.cafe/gitcafe/zed/commit/25036ba8bce904124e04c4e11e5264a3034c7f52)

Repository: [gitcafe/zed](https://git.cafe/gitcafe/zed)

Visibility: public

Requested revision: 25036ba8bce904124e04c4e11e5264a3034c7f52

Requested commit: 25036ba8bce904124e04c4e11e5264a3034c7f52

Commit: 25036ba8bce904124e04c4e11e5264a3034c7f52

Tree: 16dd88bb16d17e1d6c4c6a2195841ec76612f72b

Author: Joseph T\. Lyons

Committer: GitHub

## Message

```
Handle new profile form in migrate_settings and migrate_language_setting (#53681)

I noticed that there are helper migration functions that apply settings
transformations to multiple layers (root, platform, release-channel, and
profile):

`migrate_settings`
`migrate_language_setting`

Both of these handle the old settings profile forms, so I've updated
them to handle either form, for usage in historical and future
migrations.

Migration `m_2026_04_10` actually introduced a wrapper function to
provide to `migrate_settings` to handle both forms, which is what clued
me into the fact that I missed these migration helpers when I wrote the
`m_2026_04_01` originally (I didn't know they existed).

Self-Review Checklist:

- [X] I've reviewed my own diff for quality, security, and reliability
- [N/A] Unsafe blocks (if any) have justifying comments
- [N/A] The content is consistent with the [UI/UX
checklist](https://github.com/zed-industries/zed/blob/main/CONTRIBUTING.md#uiux-checklist)
- [X] Tests cover the new/changed behavior
- [X] Performance impact has been considered and is acceptable

Closes #ISSUE

Release Notes:

- N/A

---------

Co-authored-by: Smit Barmase <heysmitbarmase@gmail.com>
```

## Parents

- [eee6b4c56ce1b048daeebe5b503d3ad023d21c17](https://git.cafe/gitcafe/zed/commit/eee6b4c56ce1b048daeebe5b503d3ad023d21c17?format=markdown)

[Source at this commit](https://git.cafe/gitcafe/zed/tree/25036ba8bce904124e04c4e11e5264a3034c7f52?format=markdown)
