id       = "datagrip"
name     = "DataGrip"
homepage = "https://www.jetbrains.com/datagrip/"
description = "Your powerful cross-platform IDE for relational and NoSQL databases."
icon     = "theSVG:datagrip"
executables   = ["datagrip"]

[dotfiles]

# https://www.jetbrains.com/help/datagrip/directories-used-by-the-ide-to-store-settings-caches-plugins-and-logs.html
# — the configuration directory is
# %APPDATA%\JetBrains\DataGrip<version> on Windows,
# ~/Library/Application Support/JetBrains/DataGrip<version> on macOS and
# ~/.config/JetBrains/DataGrip<version> on Linux — one configuration directory
# under three names, which is [appData]. The version is part of the name, hence
# the glob. The system directory (~/Library/Caches, ~/.cache) and the logs
# (~/Library/Logs) sit outside this tree and never come along.
paths = ["[appData]/JetBrains/DataGrip*/"]

# Same page: on Windows and macOS the plugins directory is `plugins` inside the
# configuration directory. Downloaded plugin jars are installs, not settings.
exclude = [
  "[appData]/JetBrains/DataGrip*/plugins/",
]

# https://www.jetbrains.com/help/datagrip/reference-ide-settings-password-safe.html
# — the IDE keeps passwords in the native keychain by default, but the "In
# KeePass" option stores them in the database file c.kdbx inside this same
# configuration directory. For DataGrip those passwords are the database
# credentials of every connection, so whenever the file exists it is the
# credential store. It sits inside a directory `paths` already covers, so a
# consumer has to let secret win over the directory.
secret = ["[appData]/JetBrains/DataGrip*/c.kdbx"]

# JetBrains' bundled Settings Sync plugin already carries these through a
# JetBrains Account.
self_sync = true

# No machine_lines: the settings under options/, keymaps/, colors/ and
# codestyles/ are the preferences a developer wants on every machine, and
# picking machine-local keys out of the IDE's XML would be guesswork. The data
# source definitions under options/ do carry host names, which a reviewer may
# want to look at again once there is a way to express "this key, in this XML".