v6.1.2

Fixes any remaining bugs with the mapping process introduced in v6.1.0.

v6.1.1

Fixes some bugs with the mapping process introduced in v6.1.0.

v6.1.0

This release introduces changes to the mapping process for BlockGridItem and BlockListItem. Prior to this release only the content of these classes was used in the mapping process. That's fine for 90% of use cases but sometimes you may want to use the Settings content in the case of a BlockGridItem you may even want to access the col/row span. This has been rolled out to all existing map definitions.

To use these new changes you'll need to change your map definition from MapDefinition to BlockItemMapDefinition. For example, ComponentMapDefinition becomes BlockItemMapDefinition. In addition the existing Map function which handles the Content has changed from public to protected. This new map definition does not directly map the Content class any more so if you need this feature consider using ComponentMapDefinition.

v6.0.0

This release is for version parity with v6 of Rhythm.Drop. Rhythm.Drop v6 contains some breaking changes so check the release notes!

The biggest breaking change in v6 is the renaming of Elements to Subcomponents. All mapping logic has been updated to reflect this change.

v5.0.0

This release is for version parity with v5 of Rhythm.Drop. Rhythm.Drop v5 contains many breaking changes so check the release notes!

Breaking changes

Aside from Rhythm.Drop's breaking changes this release contains breaking changes directly.

Package Dependencies

Prior to v5 any dependencies within Rhythm.Drop.Umbraco which were Rhythm.Drop.Umbraco packages were based on the current version or higher. For example:

Rhythm.Drop.Umbraco.Web (>= 4.0.0)

This didn't make any sense as breaking changes would often prevent this dependency from working out. Going forward all packages will ship with a cap at the current major version. For example:

Rhythm.Drop.Umbraco.Web (>= 5.0.0 && < 6.0.0)

This is thanks to code from the Umbraco CMS project.

New Features

• Base Map Definitions for;
  • Elements
  • Images
  • Modals
• Umbraco Mapper and Mapper Context extensions for;
  • Elements
  • Images
  • Modals

This now means all common models for Rhythm.Drop are supported in some form for Umbraco Mapper. As with Links and Components no implementations are included with Rhythm.Drop.Umbraco.Builders. These must be provided on a per project basis.

v4.0.0

This release is for version parity with v4 of Rhythm.Drop.

There are no direct features or fixes in this release.

v3.0.0

This release is for version parity with v3 of Rhythm.Drop.

There are no direct features or fixes in this release.

v2.3.2

Further fixes to UmbracoMapper and MapperContext extension methods.

This update ensures all extension methods (Components and Links) accept a nullable source which is then handled within the method itself.

XML-Docs are updated to explain expected return behavior.

v2.3.1

Fixed the following bugs;

• MapLink did not use BlockListModel?
• Some MapLink functions did not pass configureContext through

v2.3.0

This release adds optional auto DI registry of Rhythm.Drop.Umbraco.Mapping map definitions.

This is an optional feature as type loading can be expensive but a is a convenience some developers be consider worthwhile versus explicit map definition registration.

There are a number of options (all extensions are for IUmbracoBuilder);

Method	Purpose
AddRhythmDropComponentMapDefinitions	Adds map definitions that map to a IComponent
AddRhythmDropComponentCollectionMapDefinitions	Adds map definitions that map to a collection of IComponent
AddAllRhythmDropComponentMapDefinitions	Adds both of the above
AddRhythmDropLinkMapDefinitions	Adds map definitions that map to a ILink
AddAllRhythmDropMapDefinitions	Adds all of the above

As this system uses Umbraco's type loader concrete implementations can be ignored by using HideFromTypeFinderAttribute.