Improved Auth Spec & challenge endpoint#1276
Improved Auth Spec & challenge endpoint#1276Moumouls wants to merge 16 commits intoparse-community:alphafrom
Conversation
# Conflicts: # integration/test/ParseLocalDatastoreTest.js # integration/test/ParseUserTest.js # package-lock.json # src/ParseUser.js # src/__tests__/ParseUser-test.js
# Conflicts: # src/__tests__/ParseUser-test.js
Generated by 🚫 dangerJS |
Codecov Report
@@ Coverage Diff @@
## master #1276 +/- ##
=======================================
Coverage 99.94% 99.94%
=======================================
Files 60 60
Lines 5847 5869 +22
Branches 1311 1320 +9
=======================================
+ Hits 5844 5866 +22
Misses 3 3
Continue to review full report at Codecov.
|
|
Issue reported for Mongo 4.X and field name length: #1277 |
# Conflicts: # integration/test/ParseQueryTest.js # package-lock.json # package.json # src/ParseUser.js # src/__tests__/ParseUser-test.js
|
@dplewis if you have an idea on the failing integration test, |
Moumouls
changed the title
|
@Moumouls Can you update from master? |
# Conflicts: # jasmine.json # package-lock.json
|
@dplewis if you have some suggestion about the failing test ? 🙂 |
|
Can you update from master again? The new release removes the flaky tests. |
|
Done @dplewis |
|
@Moumouls how is this coming along? Would be good to have implemented for Parse Server 6 |
3 participants
Need: #1275
SDK Login update for: https://github.com/parse-community/parse-server
Note: On OSX can test integration with 3.6, and tests fails in mongo 4.0 due to invalid field name "length"
If CI pass then we have detected a regression between mongo 3.6 and 4.0 for field name
lengthon objects