feat: tickets & users types + adjustments on types exports + option to throwOriginalException #422
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Pull Request Description
Updated some types on tickets and users clients;
Updated exports config on package.json so we can import types directly from the client;
before the update
after the update
Added option on createClient to allow rethrow the original exception;
In many scenarios the lib is just swallowing the original exception by creating a new exception with just a new message prefix, this is bad because you loose all the original fields of the exception thrown by the transporter request.
This option allows the lib to throw the original exception as is and let the user decide what to do with it.
Additional Information
Documentation
Checklist