Skip to content

Update schema mismatch error to include type string #1898

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

Merged
merged 1 commit into from
May 24, 2016

Conversation

JeremyPlease
Copy link
Contributor

This is a really small change to the schema mismatch error message string.

Example schema:

{
    "className": "Rocket",
    "fields": {
        "launchTime": { "type": "Date" },
    }
}

Attempted bad request:
rocket.save({ launchTime: 'never!' })

Error response before this pull request:
"schema mismatch for Rocket.launchTime; expected [object Object] but got String"

Error response after this pull request:
"schema mismatch for Rocket.launchTime; expected Date but got String"

@codecov-io
Copy link

Current coverage is 91.79%

Merging #1898 into master will increase coverage by <.01%

@@             master      #1898   diff @@
==========================================
  Files            91         91          
  Lines          6396       6397     +1   
  Methods        1105       1105          
  Messages          0          0          
  Branches       1344       1345     +1   
==========================================
+ Hits           5871       5872     +1   
  Misses          525        525          
  Partials          0          0          

Powered by Codecov. Last updated by 3a96140...2d02bf9

@drew-gross
Copy link
Contributor

Awesome, thank you!

@drew-gross drew-gross merged commit 4864518 into parse-community:master May 24, 2016
maninga added a commit to maninga/parse-server that referenced this pull request May 26, 2016
* upstream/master: (63 commits)
  Fixes parse-community#1649 (parse-community#1650)
  Update issue template (parse-community#1899)
  Break schemaController dependency. (parse-community#1901)
  Remove unnecessary null check
  Update schema mismatch error to include type string (parse-community#1898)
  Move more mongo specific stuff into mongo adapter
  Kill mongoOptions
  Consistent parameter order
  move transformWhere into mongo adapter
  Remove options from count
  Can't sort a count
  Remove limit from count
  Destructure mongo options
  remove adaptive collection call
  create + use adapter count instead of collection count
  transformWhere in MongoAdapter
  remove schemaController paramater
  Remove schemaController parameter
  Remove getRelationFields
  Remove all dependencies on schemaController
  ...
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