Breaking changes
- The type of the
TimeSeriesExtractorOptions.StartAt
property is nowJsonPointerLiteral?
instead ofJsonPointer?
. - The type of the
TimeSeriesExtractorOptions.TimestampProperty
property is nowJsonPointerLiteral?
instead ofJsonPointer?
. - The
TimeSeriesExtractorOptions.IncludeProperty
property has been replaced with a newCanProcessElement
property. The type of the new property isJsonPointerMatchDelegate
. - The existing overloads for
TimeSeriesExtractor.CreateJsonPointerMatchDelegate
have been removed and replaced with a new overload that accepts aJsonPointerMatchDelegateOptions
object. This makes it easier to managed the desired behaviour of the generated delegate.
Other changes
- Match rules that use pattern match expressions (i.e.
*
and?
for multi- and single-character wildcards respectively) no longer have to be valid JSON pointers. - When creating a delegate using
TimeSeriesExtractor.CreateJsonPointerMatchDelegate
, the options can specify if compiled regexes should be used when parsing pattern match rules.
What's Changed
- Match rule improvements by @wazzamatazz in #10
- Fix typo in version by @wazzamatazz in #11
- Make TypeConverters internal by @wazzamatazz in #12
- Add NuGet package readme file by @wazzamatazz in #13
- Update Cake tools version by @wazzamatazz in #14
- Implicit operators allow null values by @wazzamatazz in #15
- Fix recursion depth check in CanProcessElement delegates by @wazzamatazz in #16
- Add sample key template placeholder for the parent of the current element by @wazzamatazz in #17
- Update how .NET Framework targets are identified by @wazzamatazz in #18
- JsonPointer.Net update by @wazzamatazz in #19
- Update version.json by @wazzamatazz in #20
- V1.0.0 release prep by @wazzamatazz in #21
- Modify JsonPointerMatch to be a readonly struct by @wazzamatazz in #22
- Fix incorrect check for default JsonPointerMatch by @wazzamatazz in #23
Full Changelog: v0.14.0...v1.0.0