BREAKING: Lucene.Net.Documents.DateTools/Lucene.Net.QueryParser Updates #580
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
DateTools
TimeZoneInfo
when converting to/from stringNumericRepresentation
enum to allow converting to/from long in the following formats:DateTime
orDateTimeOffset
.time * TimeSpan.TicksPerMillisecond
and the conversion to output values istime / TimeSpan.TicksPerMillisecond
.Resolution
enum and renamedDateResolution
.QueryParser
Lucene.Net.QueryParsers.Flexible.Standard.Config.NumberDateFormat
: Added constructor overload to format a date without a time.Lucene.Net.QueryParsers.Flexible.Standard.Config.NumberDateFormat
: AddedNumericRepresentation
property to set the representation to use for bothFormat()
andParse()
.TimeZoneInfo
when converting to/from string (Classic and Flexible query parsers)Lucene.Net.QueryParsers.Flexible.Standard
: Changed numeric nodes to accept and returnJ2N.Numerics
types instead ofobject
.Lucene.Net.QueryParsers.Classic.QueryParserBase
: UseTryParse()
instead ofParse()
to parse numeric values. Use the current culture, but fall back to invariant culture.