Fix Schema Nullables

[1337joe]

I finally caught back up to recent schema changes. Here's a small batch of added allow_null annotations for nullable read_only fields.

I also removed the default value of '' because that's not a valid selection from the choices list (which was resulting in code generated from the schema failing to compile). As far as I've spotted the changes to parameter/parameter template don't result in changes to the UI.

[netlify]

✅ Deploy Preview for inventree-web-pui-preview canceled.

Name	Link
🔨 Latest commit	d24950d
🔍 Latest deploy log	https://app.netlify.com/projects/inventree-web-pui-preview/deploys/6961a816488bb400083ef9a7

[codspeed-hq]

CodSpeed Performance Report

Merging this PR will not alter performance

_{Comparing 1337joe:fix_api_nullables (d24950d) with master (70fcaa7)}

⚠️ Unknown Walltime execution environment detected

Using the Walltime instrument on standard Hosted Runners will lead to inconsistent data.

For the most accurate results, we recommend using CodSpeed Macro Runners: bare-metal machines fine-tuned for performance measurement consistency.

Summary

✅ 44 untouched benchmarks
⏩ 29 skipped benchmarks¹

Footnotes

1. 29 benchmarks were skipped, so the baseline results were used instead. If they were deleted from the codebase, click here and archive them to remove them from the performance reports. ↩

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 88.17%. Comparing base (70fcaa7) to head (d24950d).
⚠️ Report is 285 commits behind head on master.

Additional details and impacted files

@@            Coverage Diff             @@
##           master   #11092      +/-   ##
==========================================
- Coverage   88.17%   88.17%   -0.01%     
==========================================
  Files        1290     1290              
  Lines       58182    58182              
  Branches     1969     1969              
==========================================
- Hits        51301    51300       -1     
- Misses       6390     6391       +1     
  Partials      491      491              

Flag	Coverage Δ
backend	89.46% <100.00%> (-0.01%)	⬇️

Flags with carried forward coverage won't be shown. Click here to find out more.

Components	Coverage Δ
Backend Apps	92.01% <ø> (ø)
Backend General	93.51% <ø> (ø)
Frontend	70.85% <ø> (ø)

🚀 New features to boost your workflow:

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

[SchrodingersGat]

WARN: diff exceeds the 1MB limit, truncating output...

The API diff comparison is failing here

[1337joe]

WARN: diff exceeds the 1MB limit, truncating output...

The API diff comparison is failing here

No idea why: the entire diff fits on one screen for me when I run it locally. I just rebased to make sure I'm up to date with master and I'll look into it more if that fails again.

[matmair]

the diff seams small on my local instance as well; looking into it

[1337joe]

I found a tool that gives a browser-viewable version of the generated change log and it is indeed massive (in part because changes to parameters makes it report changes to everywhere parameters are available). I should have time this afternoon to figure out if this is valid or if I need to split my changes to make the diff easier to review.

[1337joe]

Long story short: changing the schema for parameters (such as allowing updated_by_detail to be nullable) results in reported changes for every api that has a detail field that includes parameters.

I rebased to pick up the new api_version changes and reduced the scope of my changes to try to fit within the tool for easier review.