ModelService: in update(), exclude_unset instead of exclude_none

[Tatsh]

With the current code set to use exclude_none this excludes fields from the schema even if None is a valid option. That means a model field that is nullable cannot be set to None with a PATCH.

I am fairly certain you meant to put exclude_unset here.

[codecov-commenter]

⚠️ Please install the to ensure uploads and comments are reliably processed by Codecov.

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 98.04%. Comparing base (6a592c1) to head (4e5846e).
⚠️ Report is 13 commits behind head on master.
❗ Your organization needs to install the Codecov GitHub app to enable full functionality.

Additional details and impacted files

@@            Coverage Diff             @@
##           master     #288      +/-   ##
==========================================
+ Coverage   98.01%   98.04%   +0.03%     
==========================================
  Files          68       68              
  Lines        2770     2813      +43     
==========================================
+ Hits         2715     2758      +43     
  Misses         55       55              

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

[eadwinCode]

With the current code set to use exclude_none this excludes fields from the schema even if None is a valid option. That means a model field that is nullable cannot be set to None with a PATCH.

I am fairly certain you meant to put exclude_unset here.

Yes. Thanks for the fix

[Tatsh]

Hi could you make a new release with this fix? Thanks.

[oburla-centumd]

Shouldn't we use exclude_unset on patch and keep update without any of those flags? Also waiting for the fix as this way ninja-extra is quite broken.