Conversation
|
Can one of the admins verify this patch? To accept patch and trigger a build add comment ".ok\W+to\W+test." |
|
Can one of the admins verify this patch? |
3 similar comments
|
Can one of the admins verify this patch? |
|
Can one of the admins verify this patch? |
|
Can one of the admins verify this patch? |
06c05aa to
6cd6bff
Compare
|
@geekguy thanks for your contribution! would you be able to add a test case to prevent regression on this fix? |
|
Can one of the admins verify this patch? |
3 similar comments
|
Can one of the admins verify this patch? |
|
Can one of the admins verify this patch? |
|
Can one of the admins verify this patch? |
|
@slnode ok to test |
|
@geekguy thank you for the pull request. As @davidcheung already mentioned, we need a unit test to verify your change. BTW while the solution proposed here is a good short-term fix, for long term we should improve this code to correctly convert email values to lower case even for complex queries like the one shown above. User.findOne({where: {email: {inq: ["HELLO@test.com"]}}})
// should be converted to
{where: {email: {inq: ["hello@test.com"]}}} |
|
@bajtos : Can you please point me to a file where I should add test cases ? I ll also check regarding converting complex queries to lower case. |
|
@geekguy perhaps like this test case, but instead of using the returned object, it makes another call using the where-inq query, then assert the object returned? |
|
fixes #2522 |
Issue:
This line doesn't work when we have
caseSensitiveEmailset tofalseand we make queries like,User.findOne({where: {email: {inq: ["hello@test.com"]}}})Additional check for string is required.