Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

Sign up
Appearance settings

Add tests for non-primitive id #1785

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

Closed
verdie-g wants to merge 1 commit into json-api-dotnet:master from verdie-g:non-primitive-id

Conversation

Copy link
Contributor

@verdie-g verdie-g commented Aug 31, 2025

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?

Copy link
Contributor Author

This is not a JADNC issue but how values are generated with EF. The fix is to do a property.SetDefaultValueSql("gen_random_uuid"). So not sure it's worth adding tests in JADNC.

Copy link
Member

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.

verdie-g reacted with thumbs up emoji

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers
No reviews
Assignees
No one assigned
Labels
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.

AltStyle によって変換されたページ (->オリジナル) /