Add tests for non-primitive id #1785
Closed
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
This is not a JADNC issue but how values are generated with EF. The fix is to do a |
|
This looks very similar to ID Obfuscation. Thanks for bringing it up (and for finding the fix). I suspect the fix varies per database provider, so I don't think it's worth adding it to the codebase. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Closes #{ISSUE_NUMBER}
QUALITY CHECKLIST
Hi @bkoelman, I'm trying to have non-primitive ids but it's not working as expected. The use-case is to display a UUID in a compact form using base 58. The Guid is wrapped in a custom struct to do that. That wrapper should be used as far as possible until it hits the db. Using JADNC, creating a resource returns a 204 even though I'm not using a client-generated id. Any idea?