Configuration

Default configuration:

[tool.inline-snapshot]
hash-length=15
default-flags=["report"]
default-flags-tui=["create", "review"]
default-flags-ide=["create", "report"]
format-command=""
show-updates=false
default-storage="uuid"

[tool.inline-snapshot.shortcuts]
review=["review"]
fix=["create","fix"]

Note

The default flags are different if you use cpython<3.11 due to technical limitations:

[tool.inline-snapshot]
default-flags=["short-report"]
default-flags-tui=["short-report"]
default-flags-ide=["short-report"]

Changing these flags will disable pytest assert rewriting for older python versions.

• hash-length: specifies the length of the hash used by external() in the code representation. This does not affect the hash length used to store the data. The hash should be long enough to avoid hash collisions.

• default-flags: defines which flags should be used if there are no flags specified with --inline-snapshot=... and default-flags-ide or default-flags-tui are note used. You can also use the environment variable INLINE_SNAPSHOT_DEFAULT_FLAGS=... to specify the flags and to override those in the configuration file.

• default-flags-tui: defines which flags should be used if you run pytest in an interactive terminal. inline-snapshot creates all snapshots by default in this case and asks when there are values to change. This feature requires cpython>=3.11

• default-flags-ide: (insider only) defines which flags should be used if you run your tests with the "run test" button in PyCharm. inline-snapshot creates in this case all snapshots by default and reports other changes. The review flag is not supported here because inline-snapshot is not able to read user input.

  Danger

  You can use ["create","fix"] if this fits your work flow, but keep in mind that this will change your snapshot values every time you press the "run test" button and you will have to undo these changes if they are incorrect.

  What you can do instead is to replace the incorrect values with ... and run your test again. The change from ... to the new value is part of the create category, which is enabled by default.

• shortcuts: allows you to define custom commands to simplify your workflows. --fix and --review are defined by default, but this configuration can be changed to fit your needs.

• storage-dir: allows you to define the directory where inline-snapshot stores data files such as external snapshots stored with the hash: protocol. By default, it will be <pytest_config_dir>/.inline-snapshot, where <pytest_config_dir> is replaced by the directory containing the Pytest configuration file, if any. External snapshots will be stored in the external subfolder of the storage directory.

• format-command: allows you to specify a custom command which is used to format the python code after code is changed.

  ruff formatruff format & lintblackno command (default)

  [tool.inline-snapshot]
  format-command="ruff format --stdin-filename {filename}"
  

  [tool.inline-snapshot]
  format-command="ruff check --fix-only --stdin-filename {filename} | ruff format --stdin-filename {filename}"
  

  [tool.inline-snapshot]
  format-command="black --stdin-filename {filename} -"
  

  inline-snapshot will format only the snapshot values with black when you specify no format command, but requires black to be installed with inline-snapshot[black].

  The placeholder {filename} can be used to specify the filename if it is needed to find the correct formatting options for this file.

  Important

  The command should not format the file on disk. The current file content (with the new code changes) is passed to stdin and the formatted content should be written to stdout.

• show-updates: shows updates in reviews and reports.

• default-storage: defines the default storage protocol to be used when creating snapshots without an explicit storage protocol, such as external(). Possible values are hash and uuid. External snapshots created by outsource() do not currently support this setting due to some internal limitations and will always use the old hash protocol.

• test-dir: can be used to define where your tests are located. The default is <pytest_config_dir>/tests if it exists, where <pytest_config_dir> is replaced by the directory containing the Pytest configuration file, if any. This directory is used to search through all test files for external() calls and to check whether the currently saved external objects are still used in the source. It is therefore required if you want to trim unused externals. You can also specify a list of folders.