

home/user_directory/.fleet/settings.json fleet in the user directory:Ĭ:\Users\user_directory\.fleet\settings.json User settings file locationsįleet settings are stored under.

Workspace settings will remain in effect. Note that this will only reset user settings. Press Command Shift to open settings.json and clear the contents of the file. By default, files are saved automatically, so you don't need to do anything unless you have turned off the auto-save feature. If you don't know the name of the setting, type a quotation mark and try some related words to see if the required setting appears on the suggestion list.Ĭhanges are applied immediately when you save the file. In the opened tab, specify the required settings using JSON syntax.įor available settings and their descriptions, refer to Settings reference. Press Command Shift to open settings.json. If you want to edit user settings through a file, use the Command Shift or select Show settings.json in the Settings tab. User settings are managed in the Settings/ Preferences tab Command. User settings apply everywhere, except for workspaces that have their own settings.

If you are working in a collaborative environment, they will only affect you and will not be visible to your teammates. User settings are your personal settings. Ultimately, if the setting is not defined anywhere, the value from the default layer is used, which provides fallback values for all settings. If a layer with higher priority does not override a setting, the value from a lower-priority layer is used. Workspace settings – settings specified for a particular folder. These settings override the default IDE settings. These settings have the lowest priority and only apply when no other layer overrides them. In Fleet, there are multiple layers of settings:įleet default settings – settings embedded in the IDE or its plugins. This topic explains how settings work, describes the steps to configure them, and provides reference that will help you find the required setting and learn more about its meaning.

File-based approach allows for simple management and sharing of settings, at the same time providing the ability to handle more advanced scenarios like applying specific settings in a particular context. The corresponding settings are managed through a set of. Fleet provides fine-grained control over its functionality and appearance.
