We're updating the issue view to help you get more done. 

The NodeTypeRegistry properties on QueryParser and ExpressionTreeParser have been replaced by NodeTypeProvider properties

Description

This change has been made in the course of larger refactorings.

If you use these properties to customize a default QueryParser (created via QueryParser.CreateDefault), you can cast the result of the NodeTypeProvider property to CompoundNodeTypeProvider and manipulate its InnerProviders property (adding new providers/registries or removing existing ones).

It is recommended, however, to create customized QueryParsers as follows:

That way, the NodeTypeProvider property needn't be used for customization.

Status

Assignee

Fabian Schmied

Reporter

Fabian Schmied

Labels

Time tracking

0m

Components

Fix versions

Priority

Normal
Configure