DATAMONGO-1289 - NullPointerException when saving an object with no "id" field or @Id annotation. #333
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
!!! DO NOT MERGE !!! Opened for discussion.
We now use
RepositoryMetdata.getIdType()
to provide a fallback id type once theEntityInformation
does not hold an id property which is perfectly valid for mongodb. This is a bit more sophisticated than just defaulting toObjectId
but requires us to use theRepositoryMetadata
which is not available when callingRepositoryFactorySupport.getEntityInformation
.Having that said we might want to think about changing the method signature of
getEntityInformation
so it takesRepositoryMetdata
wich would allow us to access the required data.