Fix received optional parameter issue and better debuggability #81
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.
Closes #59
The issue with the received optional parameter fixed itself with just swapping the order of the override types for TerminatingObject.
This pr replaces some of the hardcoded values around the library with typed ones. It also enhances a lot the logging output of the Substitute proxies, so hopefully no more
TypeError: Cannot convert object to primitive value.Some releases back, when doing a console.log of a non mocked property you would get the TypeError described before. Now it's something like
[Function: SubstituteJS] -> add, whereaddis the last accessed property / method of the proxy before the logging.