We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Its common to have ids on objects as numbers, but make requests with the string equivalent. can.fixture should be able to handle it.
can.fixture
VOTE HERE: http://bithub.com/event/30391
The text was updated successfully, but these errors were encountered:
is there an advantage to the ID being a number? can we force to set them as strings to start with so there isn't a type mismatch?
Sorry, something went wrong.
@shcarrico Force both ids? But using == where you want type coercion makes sense. Otherwise, where should == be used.
==
I noticed this, too and this should probably be a JSHint exception. I wanted to write a test, do you have a quick example for what is failing?
Successfully merging a pull request may close this issue.
Its common to have ids on objects as numbers, but make requests with the string equivalent.
can.fixture
should be able to handle it.VOTE HERE: http://bithub.com/event/30391
The text was updated successfully, but these errors were encountered: