Transformation Object

A transformation object is used to manipulate meta variables. It is a dictionary with the following structure:

• a key that specifies which string operation will be applied to the meta variable, and
• a value that is another object with the details of how to perform the operation.

Different string operation keys expect different object values.

replace

Use a regular expression to replace the text in a meta-variable with a new text.

replace transformation expects an object value with the following properties:

replace

• type: String
• required: true

A Rust regular expression to match the text to be replaced.

by

• type: String
• required: true

A string to replace the matched text.

source

• type: String
• required: true

A meta-variable name to be replaced.

The meta-variable name must be prefixed with $.

Example:

transform:
  NEW_VAR:
    replace:
      replace: regex
      by: replacement
      source: $VAR

substring

Create a new string by cutting off leading and trailing characters.

substring transformation expects an object value with the following properties:

startChar

• type: Integer
• required: false

The starting character index of the new string, inclusively.
If omitted, the new string starts from the beginning of the source string.
The index can be negative, in which case the index is counted from the end of the string.

endChar

• type: Integer
• required: false

The ending character index of the new string, exclusively.
If omitted, the new string ends at the end of the source string.
The index can be negative, in which case the index is counted from the end of the string.

source

• type: String
• required: true

A meta-variable name to be truncated.

The meta-variable name must be prefixed with $.

Example:

transform:
  NEW_VAR:
    substring:
      startChar: 1
      endChar: -1
      source: $VAR

Pro Tip

substring works like Python's string slicing. They both have inclusive start, exclusive end and support negative index.

substring's index is based on unicode character count, instead of byte.

convert

Change the string case of a meta-variable, such as from camelCase to underscore_case.

This transformation is inspired by TypeScript's intrinsic string manipulation type.

Ideally, the source string should be an identifier in the rule language.

convert transformation expects an object value with the following properties:

toCase

• type: StringCase
• required: true

The target case to convert to.

Some string cases will first split the source string into words, then convert each word's case, and finally join the words back together. You can fine-tune the behavior of these separator-sensitive string cases by the separatedBy option.

ast-grep supports the following cases:

StringCase

Name	Example input	Example output	Separator sensitive?
lowerCase	astGrep	astgrep	No
upperCase	astGrep	ASTGREP	No
capitalize	astGrep	AstGrep	No
camelCase	ast_grep	astGrep	Yes
snakeCase	astGrep	ast_grep	Yes
kebabCase	astGrep	ast-grep	Yes
pascalCase	astGrep	AstGrep	Yes

separatedBy

• type: Array<Separator>
• required: false
• default: all separators

A list of separators to be used to separate words in the source string.

ast-grep supports the following separators:

Separator

Name	Separator character	Example input	Example output
Dash	-	ast-grep	[ast, grep]
Dot	.	ast.grep	[ast, grep]
Space		ast grep	[ast, grep]
Slash	/	ast/grep	[ast, grep]
Underscore	_	ast_grep	[ast, grep]
CaseChange	Described below	astGrep	[ast, grep]

CaseChange separator is a special separator that splits the string when two consecutive characters' case changed. More specifically, it splits the string in the following two scenarios.

• At the position between a lowercase letter and an uppercase letter, e.g. astGrep -> [ast, Grep]
• Before an uppercase letter that is not the first character and is followed by a lowercase letter, e.g. ASTGrep -> [AST, Grep]

More examples are shown below. You can also inspect the equivalent regular expression examples to see how CaseChange works in action

RegExp -> [Reg, Exp]
XMLHttpRequest -> [XML, Http, Request]
regExp -> [reg, Exp]
writeHTML -> [write, HTML]

source

• type: String
• required: true

A meta-variable name to convert.

The meta-variable name must be prefixed with $.

Example:

transform:
  NEW_VAR:
    convert:
      toCase: kebabCase
      separatedBy: [underscore]
      source: $VAR

Suppose we have a string ast_Grep as the input $VAR, The example above will convert the string as following:

• split the string by _ into [ast, Grep]
• convert the words to lowercase words [ast, grep]
• join the words by - into the target string ast-grep

Thank Aarni Koskela for proposing and implementing the first version of this feature!

rewrite Experimental

rewrite is an experimental transformation that allows you to selectively transform a meta variable by rewriter rules. Instead of rewriting the single target node which matches the rule, rewrite can rewrite a subset of AST captured by a meta-variable.

Currently, it is an experimental feature. Please see the issue

rewrite transformation expects an object value with the following properties:

source

• type: String
• required: true

The meta-variable name to be rewritten.

The meta-variable can be single meta-variable, prefixed with $, or multiple prefixed with $$$$.

ast-grep will find matched descendants nodes of the source meta-variable for single meta-variable and apply the rewriter rules to them. For multiple meta-variables, ast-grep will find matched descendants nodes of each node in the meta-variable list.

rewriters

• type: Array<String>
• required: true

A list of rewriter rules to apply to the source meta-variable. The rewrite rules work like ast-grep's fix mode.

rewriters can only refer to the rules specified in rewriters section.

ast-grep will find nodes in the meta-variable's AST that match the rewriter rules, and rewrite them to the fix string/object in the matched rule.

rewriter rules will not have overlapping matches. Nodes on the higher level of AST, or closer to the root node, will be matched first.

For one single node, rewriters are matched in order, and only the first match will be applied. Subsequent rules will be ignored.

joinBy

• type: String
• required: false

By default, the rewritten nodes will be put back to the original syntax tree.

If you want to aggregate the rewrite in other fashion, you can specify a string to join the rewritten nodes. For example, you can join generated statements using new line.

Example:

transform:
  NEW_VAR:
    rewrite:
      source: $VAR
      rewriters: [rule1, rule2]
      joinBy: "\n"

Thank Eitan Mosenkis for proposing this idea!