Skip to main content

Extension Settings

Extension Settings#

The extension exposes multiple settings to allow you to change certain extension features.

You can access the Extension Settings by:

  • On Windows: Selecting File > Preferences > Settings, then expanding Extension and clicking
  • On Mac: Selecting Code > Preferences > Settings, then expanding Extension and clicking

Configuration Settings#

As of version 6.2.0 it is no longer necessary to configure application ids in the extension settings. As such the 'Config: Applications' setting has been removed. If you used a version prior to 6.2.0, then any applications you configured will still appear in your settings, but they will no longer be used. Changes to the Application setting will have no affect. The applications the user can sign in to are now fetched at sign in, making the need to configure the application ids obsolete.

  • Config: Application ID - The ID of your current application as registered on . You may need to contact your account administrator to get this.
  • Config: Enable App Level Items - A setting that enables the ability to manage scripts and user configs at the application level, default is off
  • Config: Enable Workspaces - A setting to allow the extension tree to show both Projects and Workspaces, default is off
  • Config: Environments - A JSON configuration the specifies the different environment urls, names, access keys, and secret keys Example for .config.environments:
[  {      "env": "https://sandbox-api.platform.com",      "name": "Sandbox (My User)",      "access": "KXZRWMYOYMADIBEWPZZCLABCNMKGJFJH",      "secret": "Rxha0isqBkP0raUUbKjjOo9s658WbptDxMLcT4pwUj0oGTrJ9tlkfaUn0v43fyog"  }]

Dev Settings#

  • Dev: Ask for Commit Messages - whether to ask the user for a commit message when scripts, user configs, and api configs are commited to Twinit, default if true
  • Dev: Open After Commit - whether the script, user config, and api config houdl re-open immediately after being commited to Twinit, default if off
  • Dev: Show Debug - Enable debug commands that may help in debugging issues with the extension, default is off
  • Dev: Show force commit commands - Enable the Force Commit commands for scripts, user configs, and api configs allowing the user to commit changes to a new version of the item even if no changes have been sensed by the Twinit IDE Extension, default is off

Local File Settings#

  • Local: Property for Script File Names - This is the property on the script NamedUserItems to use for the file names in your local workspace. Choices are the script's _name or _userType property.
  • Local: Script Extension - This is the file extension to use for scripts saved in your local workspace
  • Local: User Config Extension - This is the file extension to use for user configs saved in your local workspace

Local Script Settings#

  • Script: Run JSHint - Whether to run scripts through basic JSHint checking before committing to
  • Script: Show Script Result In - Choose to display script results in a New Document or in the extension's debug console. Us ethe Toggle Log View command to view the debug console.
  • Script: Warn To Save Before Run - Whether to warn to save the script before running the script