Preview Release v2.0.1 Available

[tsutomi]

We are making available a pre-release version of the Deveel.Webhooks framework, which introduces a lot of breaking changes in the code

• Rewrite of the Sender and Notifier services
  • The Webhooks sent are not anymore constrained to the IWebhook contract
  • A new WebhookDestination object describes the receiver-specific information and configurations (eg. address, retry-count, verification address, signatures, etc.)
  • Senders and notifier services can be segregated by the class of webhooks they handle (eg. the same application might notify two webhooks using different configurations and behaviors)
  • The two services are now less dependent from each other's
  • Enhanncing and fixing the support for LINQ filtering in the notification process
• Webhook Subscriptions management has been rewritten
  • Subscriptions are now based on the class of webhooks to be subscribed
  • The multi-tenancy is now implemented using the functions provided by the Finbuckle.MultiTenant library, to make it more standard and supported by the community
  • The storage contract is now slimmer and allows more extensions, such as the possibility of other implementations (eg. Entity Framework)
  • The MongoDB implementation of the storage is now based on MongoFramework, removing the custom implementation made within the project
• New Webhook Receiver implementation based on ASP.NET Core stack (introduced in the version v1.1.7)
  • The architecture of the receiver is not dependent on the inheritance of the webhooks from the IWebhook contract
  • The library introduces Middlewares that can be wired up in the application pipelines
  • Multiple webhook types can be received, segregating the classes of webhooks handled by the receiver: the same ASP.NET Core application can receive webhooks from two or three different providers, or from the same provider in multiple formats (eg. one webhook class might represent an incoming message in a form, while another class might rapresent the status changes of a message sent).

Note - Because the beaking changes of the overall framework, we want to give some time to the projects adopting it to report errors or requests of changes, before releasing a stable new version.