roadtoagility / dflow Goto Github PK

Now we have to do an unnecessary implementation of the method Update in all subscribers

All of our tests are in Example project, do we to test the core and implement all missing classes as default implementations.

Define operational events, like:

CommandEvent: atributtes: {status: enum - succed: true | false, exception: ExceptionClass, detail: "additional text information", data: GenericDataType to the user}

Domain needs to provide just domain modeling tools, no validation relying on an external libraries like FluentValidation.

Develop a publishing workflow

What you think about setup warnings as errors on build?

@drr00t @dougramalho

I have found this Github Action https://github.com/cycjimmy/semantic-release-action to impove a best way to realese, for use them need to use semantic commit menssage pattern

.vs/* from root folder

DFlow has two different types of business object:

• Entities
• Value Objects

Both are responsible for:

• Enforce the existing rules for the concept that they represent, like:

Money internally is a numeric type, and has rules like least value is 0, and maybe a top limit value.

So, for those do we use:

• read-only object rule enforced by private constructors and supported by factory methods
• Existential validations rely on Validator object implement with FluentValidator
• Transport validation error to parent object like Entity via property ValidationResults

We really would like to remove FluentValidator dependency and to have our own implementation of Chain of Responsibility desing pattern but we can't lose factory method object building style.

One thing that could be nice is to concepts like ValueOf library and implement validation integrated to Object construction.