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

Investigate if switching edits to JsonPatch endpoints makes sense #647

Open
hhyyrylainen opened this issue Jun 9, 2023 · 0 comments
Open

Comments

@hhyyrylainen
Copy link
Member

There's inbuild support for patching a resource (updating it) in aspnet: https://learn.microsoft.com/en-us/aspnet/core/web-api/jsonpatch?view=aspnetcore-5.0

Currently a custom properties copy is used instead. Maybe switching to the standard way would be okay? Though, it needs the newtonsoft JSON and doesn't seem to have a way to disallow certain properties from being updated...

@hhyyrylainen hhyyrylainen added this to Backburner in Thrive Planning via automation Jun 9, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
Thrive Planning
  
Backburner
Development

No branches or pull requests

1 participant