You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We receive a lot of various error reports (on StackOverflow, GitHub, support chat on intercom) that all have one common denominator: they are caused by a missing registration of the ITypeProvider implementation.
For simplicity (and historical reasons), the registration is not included in the README (so probably a lot of people miss it at that point).
The fact is that the ITypeProvider is not required for the simplest scenarios such as retrieving a 1st level model without complex types. However, for anything more complex (linked items, rich text, etc.) it absolutely necessary to have it registered.
Proposed solution
We have a few options:
link the wiki page from the readme
make the readme a bit longer and add the registration there + link the wiki page
Motivation
We receive a lot of various error reports (on StackOverflow, GitHub, support chat on intercom) that all have one common denominator: they are caused by a missing registration of the
ITypeProvider
implementation.There are more ways to register the implementation and they are described here: https://github.com/Kentico/kontent-delivery-sdk-net/wiki/Working-with-strongly-typed-models#adding-support-for-runtime-type-resolution
For simplicity (and historical reasons), the registration is not included in the README (so probably a lot of people miss it at that point).
The fact is that the
ITypeProvider
is not required for the simplest scenarios such as retrieving a 1st level model without complex types. However, for anything more complex (linked items, rich text, etc.) it absolutely necessary to have it registered.Proposed solution
We have a few options:
ITypeProvider
mandatory and throw an exception if omittedYour opinion
Let us know what would be an appropriate solution for you (if you were a new user of the SDK).
The text was updated successfully, but these errors were encountered: