12.1.0

https://www.nuget.org/packages/Kentico.Kontent.Delivery/12.1.0

• Items feed exposes the current continuation token. Use the ContinuationToken property of the DeliveryItemsFeedResponse.
• Items feed is easier to mock and test. Use the IDeliveryItemsFeed interface to create your own.

12.0.0

https://www.nuget.org/packages/Kentico.Kontent.Delivery/12.0.0

New features

• Response models provide information whether content is stale. Use the HasStaleContent property to determine content status.
• Items can be enumerated in a streaming fashion. Use the GetItemsFeed method to create a feed. Use the HasMoreResults property and the FetchNextBatchAsync method to enumerate the feed.

Breaking changes

• GetTaxonomyAsync, GetTypeAsync and GetContentElementAsync methods return response models instead of taxonomy group, content type or content type element models. Use Taxonomy, Type or Element properties to get response content. There is also an implicit conversion from response models to their content.
• Improved retry policy. Apart from error responses it also handles connection issues and it no longer depends on Polly. Use the WithDefaultRetryPolicyOptions method to customize settings of the default retry policy. Create a custom retry policy by implementing IRetryPolicy and IRetryPolicyProvider interfaces.
• Updated client options.
  • Use the UseProductionApi method instead of the UseProductionApi property.
  • Use the WaitForLoadingNewContent method instead of the WaitForLoadingNewContent property.
  • Use the UseProductionApi method with a secure access key parameter instead of the UseSecuredProductionApi method when secure access to the Delivery API is enabled.
  • Use UseSecureAccess and SecureAccessApiKey properties instead of UseSecuredProductionApi and SecuredProductionApiKey properties to configure client when secure access is enabled.

11.0.3

https://www.nuget.org/packages/Kentico.Kontent.Delivery/11.0.3

11.0.2

Update Nuget icon.

11.0.1

Breaking changes

• Kentico Cloud is now Kentico Kontent.
  As we finalize our move to Content as a Service, we decided to reflect that in our brand so we renamed repository, Nuget feed, namespaces, and all related code.

11.0.0

Breaking changes

• Kentico Cloud is now Kentico Kontent.
  As we finalize our move to Content as a Service, we decided to reflect that in our brand so we renamed repository, Nuget feed, namespaces, and all related code.

11.0.0-beta1

New features

• Response models provide information whether content is stale.

Breaking changes

• GetTaxonomyAsync, GetTypeAsync and GetContentElementAsync methods return response models instead of taxonomy group, content type or content type element models. Use Taxonomy, Type or Element properties to get response content. There is also an implicit conversion from response models to their content.

10.0.1

https://www.nuget.org/packages/KenticoCloud.Delivery/10.0.1

Fixes:

• #160 - GetExecutingAssembly() is not accesible in Xamarin.

10.0.0

https://www.nuget.org/packages/KenticoCloud.Delivery/10.0.0

Fixes:

• #152 - Code First approach
• #153 - Inline content resolver in v9 has unnecessary wrapping

Breaking changes:

• ResolvedContentItemData class was removed as it served just as an unnecessary wrapper class

• Every "code first" occurence in the code was removed i.e.:
  • ICodeFirstModelProvider, ICodeFirstTypeProvider and ICodeFirstPropertyMapper interfaces where renamed to IModelProvider, ITypeProvider and IPropertyMapper
  • Methods for registration in DeliveryClientBuilder - WithCodeFirstModelProvider, WithCodeFirstTypeProvider and WithCodeFirstPropertyMapper were renamed to WithModelProvider, WithTypeProvider and WithPropertyMapper
  • CodeFirstResolvingContext class was renamed to ResolvingContext

9.0.1

https://www.nuget.org/packages/KenticoCloud.Delivery/9.0.1

Fixes:

• #145 - Missing content model causes DeliveryClient to silently fail
• #146 - Resolving inline items with IInlineContentItemsResolver is broken
• #149 - Custom default inline content items resolver registered through builder is not used

New features:

• some interfaces were removed or made simpler

Breaking changes:

• Non-generic IInlineContentItemsResolver was removed as it was an unusable interface that might eventually cause confusion in combination with ITypelessInlineContentItemsResolver.
• removed members from IInlineContentItemsProcessor

Non-breaking changes:

• An independent ITypelessInlineContentItemsResolver interface was introduced to wrap and hide IInlineContentItemsResolver<TContentItem> resolvers and provide them in a non-generic way to the InlineContentItemsProcessor that later puts inline content items through the resolver in order to obtain their string representation.
• New extension methods for IServiceCollection were introduced to allow registration of custom inline content items resolvers