Liquid-Application-Framework-1.0-deprecated
Liquid-Application-Framework-1.0-deprecated copied to clipboard
ava-innersource
Liquid is a framework to speed up the development of microservices
Right now, message-driven controllers (_workers_) have to both annotate themselves with `MessageBus` and implement an abstract class called `LightWorker`. Having a base class follows Liquid principle of being very opinionated...
The term `Critic` is used throughout Liquid's code (`Critic`, `ICriticHandler`, etc.): https://github.com/Avanade/Liquid-Application-Framework/blob/1f805007f58b73ae09067bc56f863ae0fa702224/src/Liquid.Base/Interfaces/CriticHandler/ICritic.cs#L10 This is a *literal translation* of the word in portuguese ("crítica"). The intent of the developer, I believe,...
ASP.NET Core provides two abstract classes for your controllers to inherit from. Those are [Controller](https://docs.microsoft.com/en-us/dotnet/api/microsoft.aspnetcore.mvc.controller?view=aspnetcore-3.0) and [ControllerBase](https://docs.microsoft.com/en-us/dotnet/api/microsoft.aspnetcore.mvc.controllerbase?view=aspnetcore-3.0). The former brings support to Views, while the latter doesn't, keeping only the...
All methods on `ILightLogger` can be mapped to `ILightTelemetry.TrackTrace`, but there's no way to do so. That would be one way to justify having both and solve #29.
Fix analyser warnings in Liquid.Runtime.
Fix analyzer warnings in Liquid.Repository.
Fix analyzer warnings in Liquid.OnPre.
Fix analyzer warnings in Liquid.OnGoogle.
Fix analyzer warnings in Liquid.OnAzure.
Fix analyzer warnings in Liquid.OnAWS.
Metadata
Owner
Metadata
Liquid is a framework to speed up the development of microservices