-
-
Notifications
You must be signed in to change notification settings - Fork 4.3k
change(model): setDataValue shouldn't set attribute as changed when u… #9347
New issue
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
Conversation
|
@sushantdhiman, can you please take a look? |
sushantdhiman
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
New test should be using .set not .setDataValue
|
@sushantdhiman, but we are checking functionality of |
sushantdhiman
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I see there is already a test for .set primitive null case.
Just move this test under new describe and rebase your branch with master. Then it should be good to go
test/unit/instance/changed.test.js
Outdated
| expect(user.changed('meta')).to.equal(false); | ||
| }); | ||
|
|
||
| it('should return falsy for unchanged primitive via setDataValue', function() { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
move this one new test under describe('setDataValue'), as it's testing setDataValue
…from null to null v3 port of sequelize#9347
…pdated from null to null #5004
Pull Request check-list
Please make sure to review and check all of these items:
npm run testornpm run test-DIALECTpass with this change (including linting)?Description of change