[LUCENENET-572] Make Lucene.Net.Expressions Configurable via Dependency Injection

• Type: Improvement
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Affects Version/s: Lucene.Net 4.8.0
• Fix Version/s: Lucene.Net 4.8.0
• Component/s: Lucene.Net.Expressions
• Assignee: Unassigned
• Reporter: Shad Storhaug
• Created: 06/Apr/17 07:05
• Updated: 24/Apr/17 00:16
• Resolved: 13/Apr/17 00:41

Description

Lucene.Net.Expressions currently reads its function data from a configuration file using Support.Configuration classes. We should aim to "push" the configuration down from the consuming application rather than "pull" it from a source that the consuming application does not control.

In Java, the initial list of functions was in an embedded text file, and it could be extended by passing in a ClassLoader (which is roughly equivalent to .NET's Assembly class). For some reason, the .NET implementation has some auto-generated wrapper code, and it is unclear what auto-generated it and if it can be re-generated. We need to investigate why the implementation is so different, and make it Dependency Injection friendly.

After this task is complete the Support.Configuration namespace should be deleted. All configuration should be supplied directly by the consuming application, not pulled from configuration files.