CrSerializer changelog

Changelog History

Page 1

• v0.9.1 Changes

  February 07, 2020

  🐛 Bug Fixes

  • 🛠 Fix issue with exclusion policies and IgnoreOn* annotations #19
  • 🛠 Fix issue with serializing ReadOnly properties 65c527c

• v0.9.0 Changes

  January 15, 2020

  • 🔨 Refactors the syntax to use a more individual annotation approach
  • 👍 Abstracts the logic to support the same annotations for various formats
  • ➕ Adds some additional features like exclusion strategies

• v0.8.2 Changes

  July 14, 2019

  🐛 Bug Fixes

  • 🛠 Fixes an issue related to the compiler bug crystal-lang/crystal#7960 resulting from some removing some leftover testing code in last release.

• v0.8.1 Changes

  July 14, 2019

  🐛 Bug Fixes

  • 0️⃣ Sets the ivar default value directly to avoid setter type restrictions.

• v0.8.0 Changes

  June 07, 2019

  🐛 Bug Fixes

  • 🛠 Fixes some issues with the specs and updates ameba dependency to support Crystal 0.29.0

  🔄 Changes

  • 💥 breaking Custom assertions should now include CrSerializer::Assertions::Assertion instead of inheriting from it.

• v0.7.1 Changes

  April 22, 2019

  🐛 Bug Fixes

  • 💥 breaking Fix a name conflict when a model has a property named errors
    • CrSerializer errors are now accessed via .validation_errors.

• v0.7.0 Changes

  April 20, 2019

  🔋 Features

  💥 Breaking Changes

  • Validation methods now must be called directly on the model. No need to include the .validator.
    • model.valid? vs model.validator.valid?.
  • 👀 When including CrSerializer, a generic type must be included that determines the format that should be supported. See the docs for more info.

• v0.6.3 Changes

  March 30, 2019

  🐛 Bug Fixes

  • 🛠 Fix a name conflict when a model has a property named groups

• v0.6.2 Changes

  March 30, 2019

  🐛 Bug Fixes

  • 🛠 Fix issue with serializing structs

• v0.6.1 Changes

  March 30, 2019

  🐛 Bug Fixes

  • Structs including CrSerializer can now correctly deserialize from json/yaml strings.

• 1
• 2
• Next ›
• Last »