Issue #160771 introduced the concept of "contexts" into code templates. The next logical step is to allow code templates with the same name so long as the contexts don't overlap.

For example, you could have multiple code templates named "log". If the context is CLASS, it would add a logger instance as a field. If the context is METHOD, it would add a logging statement.

Organized properly, this could vastly reduce the number of template abbreviations developers would need to remember, since related items can be grouped under the same name instead of having to use a unique (and almost by definition harder to remember) name for each template. For example, currently the logger instance must be added with the "logr" abbreviation, which is not obvious.