On Thu, Jun 1, 2017 at 4:12 AM, Andrias Sundskarð <a...@amc.dk> wrote:
> That might work, but I'm thinking that the type coercer solution is more > like "code once, fix every page", right? Right. Or you could create a new class wrapping a collection and contribute a coercion for it to GridDataSource, avoiding trying to override an existing coercion. > However, the question on how to replace an existing type coercer remains. > Is that not possible? > I may be wrong and I haven't tested, but I don't think so. I'm very curious on why you want or need to override this coercion in first place.
