-
Enhancement
-
Resolution: Fixed
-
P3
-
None
-
repo-panama
Since ScopedAccessException should never be visible in user code, unless something extremely bad happens (e.g. failure to dleiver the async exception in time), this exception should:
1) be turned into an Error
2) have stack trace disabled (since it's a singleton, anyway)
3) have some explanatory text as to what happened
1) be turned into an Error
2) have stack trace disabled (since it's a singleton, anyway)
3) have some explanatory text as to what happened