have_type
comparison consistency improvements
#25
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.
What is the current behavior?
Currently, we're assuming that actual
type
is always a string, which causes test failures whenevertype
is a symbol.In my case it is caused by those lines of
JSONAPI::Serializable::Resource
:It always transforms
type
to a symbol so the tests fail ashave_type
compares it to a string.What is the new behavior?
The actual
type
is transformed into a string for a comparison consistency.Checklist
Please make sure the following requirements are complete:
features)