Adding Dapper.Contrib Attributes to model carries dependency with Dapper library (and dapper.Contrib)

Hi,

I have been using dapper and dapper.contrib for years. Common use case is you have a project with your POCs. i.e. WhateverCompany.Model. Usual scenario is you expose "some" of this objects to the outside world, i.e. "Products" in the form of a package, so some contracts will carry the "Product" entity.

The problem comes when your customers need to add dapper dependency as it is required for attributes as "ComputedAttribute", "TableAttribute", etc. In few words, packaging the "Model" project will add "Dapper" and "Dapper.Contrib" packages which is not ideal, as you are only decorating one property with an attribute. I.e.:

[Computed]
public DateTime? EffectiveDate { get; set; }

I think it would be ideal if you would package these attributes in a smaller project, so there is not a dependency with the whole Dapper project, or else use reflection in a way that would allow to import (copy) these attributes to the own project, which actually works for the "TableAttribute" but not for the rest of them.

This way the Repo project would need this Dapper dependency, but the Model project and all the referencing clients wouldn't need to add this dependency to the projects.

Thanks

Start by reviewing the definitions and package dependencies for ComputedAttribute, TableAttribute, and the other Dapper.Contrib attributes mentioned in the issue. Determine whether the attributes can be isolated from the main Dapper dependency so model projects can reference them without bringing in Dapper; done means the model package no longer requires those dependencies while repository usage remains supported.