Skip to main content

Default / directory settings

Are you using only one endpoint in your project and you are tired of pasting {{ env.endpoint }} into every endpoint field? Do you want to use gRPC-Web for a bunch of operations which are all in the same directory? Or do you want to ignore the TLS server certificate validation for all operations when working locally? Then this feature is for you.

Note that this are default settings. You can still overwrite them in folders and operations.

Project default settings​

Project default settings apply to the whole project (unless overwritten of course). In the menu, click Project → Default settings to access the default settings.

info

Setting values in the General tab applies them to all "technologies" (e.g. REST or gRPC). Specifying values in a "technology tab" overrides values defined in the General tab.

In the above example, a default endpoint has been configured for all environments and technologies. These settings will apply as long as they are not overwritten via directory default settings or in the operation itself.

Directory default settings​

You can also configure default settings for a directory, which only apply to subdirectories and operations within that directory. To do that, select a directory in the operation list.

If you specify values in the directory default settings, they will overwrite the values defined in the project default settings and parent directory settings. However, if you leave some values empty, the project (or parent directory) default values will still apply.

In the above example, you can see that the REST endpoint was left blank and thus the project default settings still applies.

Default settings for a specific environment​

By default, default settings will be applied regardless of the currently active environment. Sometimes, it is useful to specify default values only for specific environments.

In the example, the server certificate validation was disabled, but only for the selected "test" environment.

Clarifications​

If default values are left blank, they are ignored (meaning that the "parent" default values apply).

Arrays of default values, such as gRPC metadata or REST headers, can only be appended to. If needed, you can ignore all inherited values, overwriting any values set by parent settings.

Default settings (ex. the endpoint) are applied in the following order (higher numbers are applied later and thus overwrite previous default settings):

  1. Project default settings
  2. Top-most directory settings
  3. All subdirectories in order

While applying the values of individual project or directory default settings, the order of precedence is (with higher numbers overwriting previous stages):

  1. General directory default settings (for all environments)
  2. Technology specific (e.g. REST) directory default settings (for all environments)
  3. General directory default settings (for the current environment)
  4. Technology specific (e.g. REST) directory default settings (for the current environment)

Operation settings (values set directly in the operation) always take precedence.