Liquid-Application-Framework-1.0-deprecated
Liquid-Application-Framework-1.0-deprecated copied to clipboard
Liquid is a framework to speed up the development of microservices
Fix analyzer warnings in Liquid.Middleware.
Fix analyzer warnings in Liquid.Domain.
Fix analyzer warnings in Liquid.Base.
Fix analyzer warnings in Liquid.Activation.
`DomainResponse` is a core concept of the framework: It represents a business result. This class is competely dependent to Json.NET as every property has some kind of reference to the...
`DomainResponse` has a `PayLoad` property that represents the actual value of a business operation. Currently, this property is of type `JToken`, making it awkward to use as we always have...
`LightViewModel`s are used to represent input data from the client. The `LightController` has a `ValidateInput` method that collects any validation error and stores inside a variable called `_inputValidationErrors` (which is...
Inside the `LightController` class, there's a method called `Result` that returns the appropriate `IActionResult` depending on the state of the `DomainResponse` passed as parameter. https://github.com/Avanade/Liquid-Application-Framework/blob/93f7874f2ead13d3602cc39fc1e9355206217f57/src/Liquid.Activation/Controller/LightController.cs#L63-L85 This method logs the response...
There's no clear purpose for [`LightBackgroundTask`](https://github.com/Avanade/Liquid-Application-Framework/blob/1f805007f58b73ae09067bc56f863ae0fa702224/src/Liquid.Activation/BackgroundTask/LightBackgroundTask.cs). One one hand, it's a simple implementation of `IHostedService`, with little functionality added (looped executing of `ProcessAsync `while `!IsCancellationRequested`, it seems). There's no need...
Liquid has a custom way of obtaining configurations. It has many issues: ### It's accessed statically by client classes This means *tight coupling* between configuration and the client class, which...