Skip to content
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

add field name to an exception #1237

Merged
merged 1 commit into from
Sep 24, 2018
Merged

add field name to an exception #1237

merged 1 commit into from
Sep 24, 2018

Conversation

toli
Copy link

@toli toli commented Apr 4, 2018

When a field is not set, i'd be nice to know what field it is - currently we are seeing just Value cannot be null and we start the scavenger hunt to find out what the field is.
Would be good to show field names for ever missing (null) field

When a field is not set, i'd be nice to know what field it is - currently we are seeing just `Value cannot be null` and we start the scavenger hunt to find out what the field is.
Would be good to show field names for ever missing (null) field

Signed-off-by: Toli Kuznets <toli@harness.io>
@evanchooly evanchooly added this to the 1.4.0 milestone Sep 24, 2018
@evanchooly evanchooly merged commit 2086790 into MorphiaOrg:master Sep 24, 2018
VPriesnitz pushed a commit to VPriesnitz/morphia that referenced this pull request Oct 5, 2018
When a field is not set, i'd be nice to know what field it is - currently we are seeing just `Value cannot be null` and we start the scavenger hunt to find out what the field is.
Would be good to show field names for ever missing (null) field
@evanchooly evanchooly modified the milestones: 1.4.0, 1.5.0 Oct 16, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants