It must be possible to enable definitions and references capabilities, without using a separated symbol resolver. Currently, the KolasuServer constructor accepts a symbolResover argument - which causes the references and definitions capabilities to be enabled. However, we do not need a separated symbol resolver in those cases where symbol resolution is already implemented using the dedicated APIs in Kolasu. References will indeed be resolved during the AST post-processing phase of the parser.
Enhancement Proposal
After a discussion with @martin-azpillaga, we propose to replace the symbolResolver constructor argument with two boolean flags:
It must be possible to enable definitions and references capabilities, without using a separated symbol resolver. Currently, the KolasuServer constructor accepts a
symbolResoverargument - which causes the references and definitions capabilities to be enabled. However, we do not need a separated symbol resolver in those cases where symbol resolution is already implemented using the dedicated APIs in Kolasu. References will indeed be resolved during the AST post-processing phase of the parser.Enhancement Proposal After a discussion with @martin-azpillaga, we propose to replace the
symbolResolverconstructor argument with two boolean flags:enableDefinitionCapability: Boolean = falseenableReferencesCapability: Boolean = false