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
Hi,
in many cases in the SDK, there should be some way to give the developer the ability to track and know where exactly something went wrong if an error is thrown, like when sending the request to the Rest API, when a failure or success happens in an internal asynchronous method of the SDK, as an example if the developer did put a wrong public key, or if there is some server ( statusCode 500 ) error, the method call will fail, not all methods are covered with throwing an exception, so the result will be a complete silence for the developer, not knowing what exactly goes wrong.
A logger using dart;developer's log() method will absolutely be helpful in tracking the process, this could be an example of the target result:
// ! Debug Console// [ YCPay ] Public key and is set.// [ YCPay ] Card information of CUSTOMER NAME is initialized.// [ YCPay ] Payment with the card is ready to use.// [ YCPay ] Starting payment request to the server.// ...
and so on, the same thing for triggering errors, as an example if the developer did set a publish key that is invalid ( doesn't meet your key generation criteria ), an error log will inform him:
// [ YCPay ] Public key is invalid.
I hope you get the target expectation.
The text was updated successfully, but these errors were encountered:
Hi,
in many cases in the SDK, there should be some way to give the developer the ability to track and know where exactly something went wrong if an error is thrown, like when sending the request to the Rest API, when a failure or success happens in an internal asynchronous method of the SDK, as an example if the developer did put a wrong public key, or if there is some server ( statusCode 500 ) error, the method call will fail, not all methods are covered with throwing an exception, so the result will be a complete silence for the developer, not knowing what exactly goes wrong.
A logger using
dart;developer
'slog()
method will absolutely be helpful in tracking the process, this could be an example of the target result:and so on, the same thing for triggering errors, as an example if the developer did set a publish key that is invalid ( doesn't meet your key generation criteria ), an error log will inform him:
// [ YCPay ] Public key is invalid.
I hope you get the target expectation.
The text was updated successfully, but these errors were encountered: