Test Partial Profiles

[sandy081]

Refs: #156144

• win @aiday-mar
• mac @anthonykim1
• linux @connor4312

Complexity: 4

Create Issue

---

Introduction

You can now create a partial profile, ie., a profile in which you can customise only some configurations (Settings, Keyboard Shortcuts, User Snippets, User Tasks, Extensions). When such a profile is active, VS Code uses the customisations from default profile for those configurations which are not part of the profile. For example: You can have a Profile with all configurations except for Keyboard Shortcuts, and use Default Profile for it.

You can create such a profile using the new Create Profile flow (Settings Gear > Profile > Create Profile...) in which you can select what can be configured in the profile.

Testing

Creating

Test creating a partial profile with various options available in the create profile flow

• Empty (Copy from None)
• Copying from a template
• Copying from existing profile

and make sure the partial profile is created and applied as expected. Please play around with this flow and provide feedback.

Editing

You can update these options after creating the profile using Settings Gear > Profile > Edit Profile... action. Try editing the profile and changing the options and test if the update is working as expected.

Other Features

• Test exporting such a profile
• Test such profiles are synced as expected across machines (You can use different user-data-dir and extensions-dir and launch VS Code for testing syncing)

[tanishqmanuja]

Use case: #156144 (comment)

Is there a PR associated for partial profiles or will it be in Insiders for testing?

[sandy081]

@tanishqmanuja This is the issue you might want to comment in - #188612

[aiday-mar]

Hey @sandy081, I am testing the partial profiles. While testing, I had the following thoughts:

1. I created an empty profile that only configures the settings and the keyboard shortcuts, meaning that the extensions were inherited from the default profile. Upon creation, I noticed that all my extensions were enabled, while in the default profile some were disabled. Do you think it would make sense to inherit also the disabled/enabled states from the default profile?
2. When I clicked on Edit Profile..., I noticed that the checkboxes that are enabled are not always the same as the ones that were previously checked during profile creation. Here is a video showing what I mean:

Screen.Recording.2023-07-25.at.10.33.46.mov

I was wondering if this was intended? For my Test Python profile, on clicking Edit profile..., I expected to see only settings, user tasks and extensions checked.

3. I am unsure if I am testing wrong, but I am having trouble syncing the profiles across different vscode instances in different user directories. Here is a video showing what I mean. Should I have seen the Test Angular profile appear in the second instance too?

Screen.Recording.2023-07-25.at.10.51.05.mov

[sandy081]

@aiday-mar

Do you think it would make sense to inherit also the disabled/enabled states from the default profile?

Definitely makes sense. At present this is happening because of the implementation limitation: Extensions enablement state is stored in storage. Please file a feature request for this.

I was wondering if this was intended? For my Test Python profile, on clicking Edit profile..., I expected to see only settings, user tasks and extensions checked.

I do not think it is expected. Editing the profile should retain the configuration when it was created. Please file an issue with steps to reproduce.

I am unsure if I am testing wrong, but I am having trouble syncing the profiles across different vscode instances in different user directories. Here is a video showing what I mean. Should I have seen the Test Angular profile appear in the second instance too?

I see you have not enabled Settings Sync. You have to Turn on Settings Sync for the syncing of data to happen. Sorry that I did not mention that assuming it was obvious. I would also recommend to use different extensions directory for the second instance.