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
{{ message }}
This repository has been archived by the owner on Nov 8, 2024. It is now read-only.
According to the documentation, gavel.js offers an async API to perform validation and other operations.
According to the code, this is not an async API but a wrapper that is blocking the event loop anyway.
This is bad and harmful as people thinks that the validation is non blocking (so I do not get worried about giant payloads as is off process), while at the end of the day it is.
Please deprecate and kill this API as soon as possible.
The text was updated successfully, but these errors were encountered:
I would deprecate both current sync and async API. After #155 lands, validation of a given transaction is a function that returns a validation result. There is no need to keep an overhead of classes, and thus the following API becomes cumbersome and obsolete:
Reading through isValidatable implementation I find it extremely over-engineered and complex. It gives a wrong expectation to the end user what the method actually does. Here's the usage example from the tests:
Current isValidatable operates only on the first argument. We must rework this method entirely, and start from understanding what purpose and usage it has.
According to the documentation,
gavel.js
offers an async API to perform validation and other operations.According to the code, this is not an async API but a wrapper that is blocking the event loop anyway.
This is bad and harmful as people thinks that the validation is non blocking (so I do not get worried about giant payloads as is off process), while at the end of the day it is.
Please deprecate and kill this API as soon as possible.
The text was updated successfully, but these errors were encountered: