gnaeus / entityframework.commontools Goto Github PK

Hi,

Are you willing to split the EntityFramework.CommonTools in several more fine-grained packages?
For instance, I would love to use your ISpecificationPattern in a library project I have, but I don’t need EntityFramework and therefore I didn’t to add Entity Framework as a dependency.
You could have several nuget packages like *.Core, *.Auditing, *.TransactionLog, *.Specification that have dependencies between them a let the consumer choose which packages they need.
Thanks in advance,
Nuno Pereira

Since the transaction log can become quite long, it should be possible to query for transactions by the entity id.

Is there a reason EntityId is not part of the TransactionLog type?

Are there other ways of filtering (in the db query) on entitytype (the id is in the serialized json, but that is not queryable).

EF Core contexts support an Update method which will update an entity if it exist.
When using context.Update(), the columns for tracking CreatorUserId and CreatedUTC are reset.

Is this a known problem?
If so, is this something that is on the roadmap to fix?

By default, Asp.net identity uses string PK data types (guids). There are lots of good reasons for doing so as long as you don't need a clustered index, but it's impossible to do so with this library because it wraps the columns with a nullable operator.

Example:

public interface IModificationAuditable<TUserId> : IModificationTrackable where TUserId : struct
{
    TUserId? UpdaterUserId { get; set; }
}

If TUserId in the above sample is string, then it's impossible to declare a property which will satisfy the interface.

Parameter type for interface is Guid but RowVersion property type byte[]. It is needed to replace parameter type from Guid to byte[].

class MyEntity : IConcurrencyCheckable<Guid>
{
[Timestamp]
public byte[] RowVersion { get; set; }
}

Hello!

First of all, I would like to thank you for your great job in this library.

I would like to ask you if it's possible to separate the Auditable and Trackable interfaces in a separate package and include this new package reference as a dependency to here?

I'm asking this because you did a great job in the interfaces and I would like to reuse them (as a package) in my "domain project layers" without having to add entity framework dependencies to projects that would probably not EF as ORM.

I'm aware of the #3, but since I'm only asking for the interfaces without the extensions, I guess that it would not escalate to lots of separate libraries.

For instance: Specification.cs only has dependencies from .NET Framework.

Other example: AuditableEntities.cs only have dependency to "System" package.

What do you think?

Thank you in advance!
Kind regards!

Hello!

EntityFrameworkCore.CommonTools is a great tool! Do you have a plans to update it up to EF Core 3.1?