Configure SubType via object with more customizations #5
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.
Still needs some tests, but much more robust than #4.
extend()
now accepts an options object as alternative to thesubTypeName
anderrorCode
parameters.Decreases emphasis on HTTP-related errors. (instead of passing
errorCode
, add{properties: {code: <code>}}
to theoptions
object.Adds ability to provide alternate
toString()
.Adds
parseFn()
, which can do additional processing on the SubType constructor argument. I'm primarily envisioning it as a way to wrap http error responses with an Error:Just like Make monkeypatching optional #4, makes monkeypatching optional.