stoveproject / stove Goto Github PK

• Autofac --> 4.6.1
• Autofac.Extras.IocManager --> 3.1.2
• Autofac.Extras.IocManager.DynamicProxy --> 3.1.2
• StackExchange.Redis --> 1.2.5
• EntityFramework.DynamicFilters --> 2.9.1

• Provide an Interface to implement any user defined filter.
• Filters should be driven by EntityFramework

Implement as default:

• SoftDelete

If we push events to RabbitMq or other messaging systems, EventSource won't be deserialized properly or getting exception since it is a proxied object. Event publisher already knows that where the Event published and why. Thus we can remove it.

• Newtonsoft.Json 10.0.3
• Hangfire 1.6.14
• HangfireSqlServer 1.6.14
• Hangfire.Core 1.6.14
• NLog 4.4.11

• Should work with Stove.Dapper under same NH transaction

• Stove.Dapper be able to share NHibernate transaction and policies, commit, rollback etc...

EventData to Event

This may or may not contain breaking changes. For sure needs more eye.

test case like following

 public class EventHandlerTests  
    {
        [Fact]
        public void should_work()
        {
            var resolver = IocBuilder.New.UseAutofacContainerBuilder()
                .UseStoveWithNullables(typeof(FakeBootstrapper)).UseStoveEventBus()
                .RegisterServices(s =>
                {
                    s.RegisterType<FakeBootstrapper>();
                    s.RegisterType<FakeSendToImageProcessorEventHandler>();
                    s.RegisterType<FakeVisualMappingCompletedEventHandler>();
                })
                .CreateResolver();


            var eventBus = resolver.Resolve<IEventBus>();

            eventBus.Register(typeof(VisualMappingCompletedEvent), new IocHandlerFactory(resolver, typeof(FakeSendToImageProcessorEventHandler)));

            eventBus.Register(typeof(VisualMappingCompletedEvent), new IocHandlerFactory(resolver, typeof(FakeVisualMappingCompletedEventHandler)));

            eventBus.Publish<VisualMappingCompletedEvent>(new VisualMappingCompletedEvent(), new Headers());
        }
    }


    public class FakeSendToImageProcessorEventHandler : EventHandlerBase, IEventHandler<VisualMappingCompletedEvent>, ITransientDependency
    {
        static int a ;
        public void Handle(VisualMappingCompletedEvent @event, Headers headers)
        {
            a++;
        }
    }

    public class FakeVisualMappingCompletedEventHandler : EventHandlerBase, IEventHandler<VisualMappingCompletedEvent>, ITransientDependency
    {
        static int b;
        public void Handle(VisualMappingCompletedEvent @event, Headers headers)
        {
            b++;
        }
    }

    public class FakeBootstrapper : StoveBootstrapper
    {

    }

In this case you will see a = 2, b = 2

• Create Stove.WebApi package for Asp.Net Core middleware

Hi,

thanks for your project, i have a question about dapper.
how to use the dapper in your framework.

thanks!

Hello @osoykan,

I have yet another impedance mismatch problem :).

It can be nice to have multi-mapping feature of Dapper. What do you think implementing this feature to Stove.Dapper project?

Example:
`
var sql = "SELECT P.Id, P.FirstName, P.LastName, " +
"A.Id AS AddressId, A.StreetNumber, A.StreetName, A.City, A.State " +
"FROM People P INNER JOIN Addresses A ON A.AddressId = P.AddressId; ";

db.Query<Person, Address, Person>(
sql,
(person, address) => {
person.Address = address;
return person;
},
splitOn: "AddressId"
).ToList();

`

As you know, we currently use EF6, and unfortunately it does not produce efficient queries. So, it is better to write pure SQL queries for our read model using Dapper repository.

By the way, I am ready for contribution.

• Command, SequencedCommand

• CorrelationId/CausationId approach for each command

• CorrelationId/CausationId aware Context implementation. This will provide these Ids in its context
  e.g ICommandContext {CorrelationId, CausationId} per thread.

  Enter context (command)
  Do stuff
  Save
  

• Consider removing ApplicationServices and introduce CommandHandler and provide a generic IHandles<T>

And cover all breaking changes.

Might be a bool value on IEventData as PublishToMessageBus

This code is similar to the asp.net boilerplate project
I'd say the even
Whats the difference?

Thanks

• DapperExtensions 1.5.0 --> 1.6.0
• EntityFramework.DynamicFilters 2.8.1 --> 2.9.0
• RavenDB.Client 3.5.3 --> 3.5.4
• JetBrains.Annotations 10.4.0 --> 11.0.0

It is CRUDY and carries proxied object as event body.

Rename EventBus.Trigger to EventBus.Publish behalf of cosmetic concerns about DDD language.

what‘s different with abp framework?

Error: Instances cannot be resolved and nested lifetimes cannot be created from this LifetimeScope as it has already been disposed.

• Should work with dapper under same transaction with multiple database (completed)
• Code Cleanup & Refactor existing parts