Skip to content

Fix #1591 #1626

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

Closed
wants to merge 1 commit into from
Closed

Fix #1591 #1626

wants to merge 1 commit into from

Conversation

drew-gross
Copy link
Contributor

This reverts the change that caused #1591. We'll need to come up with some strategy for handling system classes that are new in Parse Server. In the meantime, doing this means we aren't blocked from releasing 2.2.8

@flovilmart
Copy link
Contributor

Instead of reverting, could we create a test case and I'll do the fix tonight?

@codecov-io
Copy link

Current coverage is 91.41%

Merging #1626 into master will decrease coverage by -0.92%

@@             master      #1626   diff @@
==========================================
  Files            87         87          
  Lines          6154       6156     +2   
  Methods        1082       1076     -6   
  Messages          0          0          
  Branches       1278       1279     +1   
==========================================
- Hits           5682       5627    -55   
- Misses          472        529    +57   
  Partials          0          0          
  1. 2 files (not in diff) in src were modified. more
    • Misses +2
    • Hits -2
  2. File ...go/MongoTransform.js was modified. more
    • Misses +50
    • Partials 0
    • Hits -50

Sunburst

Powered by Codecov. Last updated by fcf971f

@drew-gross
Copy link
Contributor Author

It's tough to create a test case as we need to test the behaviour of Parse.com. Maybe I can add a test case on the schema collection directly or something.

@flovilmart
Copy link
Contributor

Like make sure after a Push sent, the _PushStatus don't exists on the Schema?

@drew-gross
Copy link
Contributor Author

Yeah kinda. I'll have a test case for you soon.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants