Despite of a certain use case, a separate
referenceIndexTransformation for the list of references would be consequent. Why?
symbolTransformation to transform the local
SymbolList of a view
symbolIndexTransformation to transform the global
referenceIndexTransformation to transform the references in the global
would extend the existing structure best.
References are defined by separate scopes which the
showInIndexedReferenceList attribute is assigned to. Why not using a separate pattern for transformation as well in order to avoid cross references with the normal symbolIndex, which contains the definition but not the usage of a symbol?
Basically it is possible to manipulate a symbol/reference in nearly any way. The used transformations may be different for function definitions and function calls.
Let's say you want to add different unicode characters as icons in front of those entries or do any other type specific stuff to the symbols'/reference's label before printed to a quick panel. Other examples might be different indention or added keywords, ...
Those transformations can be done by a plugin after requesting the
window.lookup_references_in_index(...) call, but maybe there will be a built-in quick panel like
Goto Reference in the future, which displays the references of a symbol under the cursor directly from the index?