!refactor(backend): restructure user endpoints#9604
!refactor(backend): restructure user endpoints#9604matmair wants to merge 7 commits intoinventree:next-breakingfrom
Conversation
✅ Deploy Preview for inventree-web-pui-preview ready!
To edit notification comments on pull requests, go to your Netlify site configuration. |
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## next-breaking #9604 +/- ##
================================================
Coverage ? 88.01%
================================================
Files ? 1295
Lines ? 58908
Branches ? 1938
================================================
Hits ? 51845
Misses ? 6581
Partials ? 482
Flags with carried forward coverage won't be shown. Click here to find out more.
🚀 New features to boost your workflow:
|
| INVENTREE_API_TEXT = """ | ||
|
|
||
| v460 -> 2026-02-27 : https://github.com/inventree/InvenTree/pull/9604 | ||
| - Refactors the user API endpoint to be less ambiguous in their naming |
There was a problem hiding this comment.
We are going to have to consider how we mix the "next-breaking" and "master" changes to the API - if we do not merge this into master we will run into conflicts.. Any thoughts how to handle this?
There was a problem hiding this comment.
My immediate idea would be to have one API bump per major release that removes all deprecations and just push the API version up by one till merge comes, but I can see that this needs some better considerations
|
moving to draft while I think about the API change that was brought up |

This realigns the user API endpoints by:
see #11433