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
Currently, the only way of viewing an exception thrown by the system is located in the backend module. However, an exception can be thrown only in the frontend context, meaning the exception would not be thrown in the backend contact. Therefore it can't be viewed and analyzed, making the debugging way harder.
Some kind of logging should be introduced in the RuntimeService which is in charge of gathering the exceptions catch during the runtime.
The text was updated successfully, but these errors were encountered:
Currently, the only way of viewing an exception thrown by the system is located in the backend module. However, an exception can be thrown only in the frontend context, meaning the exception would not be thrown in the backend contact. Therefore it can't be viewed and analyzed, making the debugging way harder.
Some kind of logging should be introduced in the
RuntimeService
which is in charge of gathering the exceptions catch during the runtime.The text was updated successfully, but these errors were encountered: