-
-
Notifications
You must be signed in to change notification settings - Fork 158
PATCH request with Nullable ID does not work. #467
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
Comments
Can you share your controller? |
Thanks |
Thanks. Do you know if the controller is being invoked at all on PATCH? i.e. are you getting 404 for route not found or because the resource cannot be found in the data store? |
I am getting a 404, no breakpoints in the PATCH function were reached. |
This sounds like an issue with the routing configuration and outside the influence of JADNC. You might try changing your route template to |
I'll look into that, but here's how I got there:
Leads me to the current fix:
Sorry, just saw your edit after I wrote it all out |
@czemanek-arm If this is still relevant, I will look into this if you can provide me with reproducible case (a branch with tests that expose your issue) |
Closing this, as it seems the discussion has stalled. Feel free to reopen if this still needs attention in v4. |
Description
Whenever a model inherits from
Identifiable<T>
and T is nullable (i.e.long?
) PATCH requests are not able to be found.This is related to my comment on #363 in that, after implimenting my work around there, I discovered that nullable ID's are unable to pick up PATCH requests in EF. POST and GET still work fine.
...
Environment
The text was updated successfully, but these errors were encountered: