Or better yet, the ability to apply regex replacement rules to the variables, such as ${TM_FILENAME,/^([A-Z])/\L$1/,/([a-z])([A-Z])/$1-\L$2/g,/..*$//}:

Snippet transform is tracked here #6920. Just having FILENAME_BASE sounds like a reasonable workaround.

stretch for August, PR welcome. See https://github.com/Microsoft/vscode/blob/master/src/vs/editor/contrib/snippet/browser/snippetVariables.ts#L85

I'll look at it this weekend.

I would love this for creating go test files. For example, if I'm in a go package a/b/c, I put my tests for package c in a/b/c/tests, its own tests package.

I have a created a snippet like the following in go.json:

{
	"Test file": {
		"prefix": "tt",
		"body": [
			"package tests",
			"",
			"import (",
			"\t\"github.com/stretchr/testify/assert\"",
			"\t. \"a/b/$1\"",
			")",
			"",
			"func Test$2(t *testing.T) {",
			"\tassert := assert.New(t)",
			"",
			"\t$0",
			"}"
		],
		"description": "Create a new test file"
	}
}

which produces

package tests

import (
	"github.com/stretchr/testify/assert"
	. "a/b/"
)

func Test(t *testing.T) {
	assert := assert.New(t)

	
}

However, if I'm in a file a/b/c/tests/foo_test.go when I expand this snippet, then the line . "a/b/" should be . "a/b/c" because these are tests for the the c package.

How do I accomplish this?

I tried using TM_DIRECTORY but it doesn't seem that I can manipulate it to remove trailing cruft. Nor can I use workspaceRoot ...

I'd really like to have access to the "parent package" but being able to manipulate the current filename with knowledge of workspace root would probably be good enough.

Will the fix mentioned in this issue support my use case (pretty common for go developers) and is there an ETA? :-)

Thanks!

Will the fix mentioned in this issue support my use case (pretty common for go developers) and is there an ETA? :-)

No, what you want is tracked here: #6920. This issue is about a pragmatic change to add a new variable which is the name of a file without its extension

@jrieken thanks for responding.

I had seen #6920 but it didn't seem immediately relevant when I first read it. I'll add my comments there.

I'll look at it this weekend.

@firelizzard18 Is this still on your radar? I don't wanna steel you thunder but I'd tackle this myself on Monday otherwise. Happy Coding

@jrieken Feel free to tackle it. Other issues have taken precedence :/