You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The current implementation of the Webhook Subscription Management feature uses a storage model that is based on an internet contract, based on the Repository pattern (IWebhookSubscriptionStore).
Deveel has recently released the Deveel.Repository project, implementing all the functions for the management of the WebhookSubscription and WebhookDeliveryResult entities.
Expected Benefits
Replacing the existing storage model with the one provided by Deveel.Repository would introduce the best practices and methods provided externally, unifying the development and maintenance efforts for both projects.
Adopting the Deveel.Repository as the model for the management of stores will also align the multi-tenant database management.
Possible Side Effects
The Deveel.Repository project has not been used (at the moment of this issue, 10/13/2023) by external projects that would extend its base CRUD functions, and at its possible that the migration will cause some incompatibilities.
The text was updated successfully, but these errors were encountered:
The current implementation of the Webhook Subscription Management feature uses a storage model that is based on an internet contract, based on the Repository pattern (
IWebhookSubscriptionStore
).Deveel has recently released the Deveel.Repository project, implementing all the functions for the management of the
WebhookSubscription
andWebhookDeliveryResult
entities.Expected Benefits
Replacing the existing storage model with the one provided by Deveel.Repository would introduce the best practices and methods provided externally, unifying the development and maintenance efforts for both projects.
Adopting the Deveel.Repository as the model for the management of stores will also align the multi-tenant database management.
Possible Side Effects
The Deveel.Repository project has not been used (at the moment of this issue, 10/13/2023) by external projects that would extend its base CRUD functions, and at its possible that the migration will cause some incompatibilities.
The text was updated successfully, but these errors were encountered: