[SERVER-12838] invalidForStorage should return actual error Created: 21/Feb/14 Updated: 11/Jul/16 Resolved: 24/Feb/14 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | JavaScript |
| Affects Version/s: | 2.6.0-rc0 |
| Fix Version/s: | 2.6.0-rc1 |
| Type: | Improvement | Priority: | Major - P3 |
| Reporter: | Asya Kamsky | Assignee: | Scott Hernandez (Inactive) |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Backwards Compatibility: | Fully Compatible | ||||||||
| Participants: | |||||||||
| Description |
|
upgradeCheck() uses Object.invalidForStorage() and then prints the error that the method returns. Unfortunately it's not a useful message:
|
| Comments |
| Comment by Scott Hernandez (Inactive) [ 24/Feb/14 ] | ||
|
New message:
| ||
| Comment by Githook User [ 24/Feb/14 ] | ||
|
Author: {u'username': u'scotthernandez', u'name': u'Scott Hernandez', u'email': u'scotthernandez@gmail.com'}Message: | ||
| Comment by Scott Hernandez (Inactive) [ 21/Feb/14 ] | ||
|
The caller has to check for null (meaning it is okay) or throw. This how it was designed. The error messages you are seeing is the generic message, which we could change. |