v1.10.8 - No it really is null, I promise 😡

Feature

• Methods with only default parameters are considered 0-arity #127 (Thanks to @valeev)
• Accessing nested members that may be null is now completely safe ⚠ #106 (Thanks to @natehitze)

Bugs

• Nullable types that are null are now not truthy #116 (Thanks to @natehitze)
• Customised Render pipeline was not passed to partials #126 (Thanks to @EndOfTheSpline)
• Ignore case now works on IDictionary<string, object> #120 (Thanks to @Meowzz95, @senneclaeskens and @stan-sz)

v1.9.3 - Deterministically Stable

Bugs

• ValueGetters are now ordered deterministic always #99 (Thanks to @jlocke427 for reporting)

Build

• Packages should be Deterministic and and Untracked sources should be source-linked #100

v1.8.4 - Dynamic and Stable

Features

• Non ExpandoObject Dynamic types are now handled a better in the standard renderer and the compilation renderer can handle some of the new cases. Thanks to @0x15e for their contribution!

Bugs

• Negative indexes on collections will no longer thow and instead return empty. Thanks to @mingwli
• The order that values are retrieved for objects has been made more stable thanks to help from @mingwli!

v1.7.2 - Get back to me with the answer

Features

• We've added support for async lambdas when you're rendering async. #88 (Thanks to @alexdresko for reporting the missing feature)

v1.6.3 - Tell me the truth and don't be ambiguous ❓

Bugs

• The renderers were not correctly handling a case where you could get ambiguous data matches when differing by case. Both now throw an Ambiguous exception in this case which should help when this happens and you're not expecting it. #81 (Thanks to @jnferner for reporting this)
• The compilation renderer did not correctly handle truthy checks and was missing truthy checks added to the standard renderer. We've now brought them inline and simplified the generated code. #80 (Thanks to @jnferner for reporting this)

v1.5.4 - What a Cultured Individual 👑

Features

• We've added a CultureInfo override to the renderer which defaults to InvariantCulture. All of our current tests expected this so we've standardised there. You can now however override as you would like. #78 (Thanks to @impworks for the contribution)

v1.4.12 - Customisation is the name

Features

• Added overload for customising the parser pipeline while configuring your Stubble instance and added Obsolete attribute on old method of setting the pipeline. This will be removed in the next major version. #56 (Thanks to @Tasteful for contributing the change)
• Added support for overriding the HtmlEncoding when using escaped mustache tags {{{ #68 (Thanks to @mingwli for the idea)
• Added a configuration option for adding a type to be blacklisted from section iteration. #69

v1.3 - Engine overload 🏎

Features

• Add render function overload for Lambdas #55 (Thanks to @Baccanno for the request and helping work out the requirements)
• Make RenderSettings and RendererSettings public on Context #50 (Thanks to @emazv72 for the enhancement)

Fixes

• Zero Numeric literals should be considered falsey #53 (Thanks to @emazv72 for the fix)

v1.2 - Unwanted blank space 🎵

Features

• The internal enumerable exclusion list for section tags has now been moved to the renderer/compiler config and can be replaced. This came out of discussions with @rlabrecque so thanks to them. #45

Fixes

• Interpolation tags were getting extra whitespace due to a bug with our literal tag folding Thanks to @StarLeafRob for reporting #36
• Exceptions would be thrown if a member with the same name was scanned twice. Thanks to @glennawatson for reporting and contributing the fix #41
• IEnumerators were not being reset after rendering and so couldn't be reused. Thanks to @rlabrecque for finding this and contributing the fix. #43

v1.1 - How to I get outa here?

• For the first release we missed some customisation functionality from the compilation renderer. You can now add ValueGetters and EnumerationConversions to your compilation renderers. Thanks to @yufeih for noticing they were missing #32
• In this release we've added some helper methods to the ParserPipelineBuilder to help users who wan't to replace, remove and add parsers which should hopefully simplify some advanced usecases. We've also updated our docs to be more clear about our design decisions. Thanks to @CoffeeDreamLabs for bringing the lack of clarity here to our attention. #31