* Allowing flowcontrol with out exceptions
So far we used exception to handle our flowcontrol, but
Exceptions are costly. In the end we enriched our
evaluation Details with errorCode and errorMessage.
This can be also handled by the providers if desired,
to reduce the execution footprint in errornous cases,
which do not have to be exceptions.
Eg FlagNotFound - it might be the case, but in performance
critical environments, an exception rather than a normal
return, can cause overhead and can be already too costly.
Signed-off-by: Simon Schrottner <simon.schrottner@dynatrace.com>
* fix: adding reason, and removing stacktraces from errors
Signed-off-by: Simon Schrottner <simon.schrottner@dynatrace.com>
* Update src/main/java/dev/openfeature/sdk/exceptions/TypeMismatchError.java
Co-authored-by: Justin Abrahms <justin@abrah.ms>
Signed-off-by: Simon Schrottner <simon.schrottner@dynatrace.com>
---------
Signed-off-by: Simon Schrottner <simon.schrottner@dynatrace.com>
Co-authored-by: Justin Abrahms <justin@abrah.ms>
Simon Schrottner