Releases: rhythmagency/rhythm.drop.umbraco
v2.2.1
Adds overloads to IUmbracoMapper
extension methods to provide an optional Action<MapperContext>
property.
Steps were taken to insure this isn't a breaking change and the only function which modifies the MapperContext
MapComponents(IPublishedContent) has an overload to still set current page.
v2.2.0
This release adds support for Umbraco Mapper. This comes in two forms;
- interfaces and abstract classes which work with Umbraco's IMapDefinition
- Extension methods for
IUmbracoMapper
andMapperContex
t (e.g. MapComponent, MapLinks)
We've decided to target just IComponent
and ILink
for this release as this components tend to be noticeable polymorphic when used in Umbraco CMS.
IImage
was not included as this would likely be built directly in a map definition other other code because of varying things like sources and properties. If a need for MapImage comes up in the future we can explore implementing that.
v2.1.0
Adds in support for Implicit Using statements. If your project uses this feature you can now AddRhythmDrop
to your app without needing an additional using statement.
v2.0.0
The v1 release was abandoned after Rhythm.Drop v2 came out.
Breaking Changes
- Reworking builders now they are no longer in Infrastructure
v1.0.0-beta1: First pre-release
Includes 3 package;
- Rhythm.Drop.Umbraco (Entry point package)
- Rhythm.Drop.Umbraco.Infrastructure (Non-web related extensions)
- Rhythm.Drop.Umbraco.Web (Web related extensions)
Install via NuGet.
Specifics
- Rhythm.Drop.Umbraco includes
AddRhythmDrop()
methods to include Rhythm Drop with Umbraco overloads to the application. - Rhythm.Drop.Umbraco.Infrastructure includes some extensions for
ILinkBuilder
related to Umbraco encoded HTML strings for labels - Rhythm.Drop.Umbraco.Web includes some extensions for
ILinkBuilder
for gettingIPublishedContent
URLs into the link builder* and an implementation ofIModalPersistenceHelper
which makes use of Umbraco's own request cache.
* ideally this functionality would have been included in Rhythm.Drop.Umbraco.Infrastructure however the user friendly extension method required to access IPublishedContent.Url()
is in Umbraco.Cms.Web.Common not Umbraco.Cms.Core so it was included in Rhythm.Drop.Umbraco.Web.