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
In the NHibernate documentation (Chapter 4.5. Tuplizers), it's mentioned that it's possible to extend NHibernate.Tuple.Entity.DynamicMapEntityTuplizer and create a custom tuplizer. However, when attempting to do so, I found that the constructor for this class is marked as internal, which prevents users from implementing a custom tuplizer if NHibernate is used as a NuGet package.
The constructor of DynamicMapEntityTuplizer should be public, allowing developers to extend this class and implement custom tuplizers as described in the documentation.
The text was updated successfully, but these errors were encountered:
Indeed, it is internal since 2007, and that was overlooked when this example was introduced in the documentation in 2009. Since the PocoEntityTuplizer has its constructor public, it would also be more consistent.
Component tuplizers, including the dynamic one, have their constructor public, too.
In the NHibernate documentation (Chapter 4.5. Tuplizers), it's mentioned that it's possible to extend NHibernate.Tuple.Entity.DynamicMapEntityTuplizer and create a custom tuplizer. However, when attempting to do so, I found that the constructor for this class is marked as internal, which prevents users from implementing a custom tuplizer if NHibernate is used as a NuGet package.
The constructor of DynamicMapEntityTuplizer should be public, allowing developers to extend this class and implement custom tuplizers as described in the documentation.
The text was updated successfully, but these errors were encountered: