Skip to content

!refactor(backend): restructure user endpoints#9604

Draft
matmair wants to merge 7 commits intoinventree:next-breakingfrom
matmair:refactor(backend)--restucture-user-endpoints
Draft

!refactor(backend): restructure user endpoints#9604
matmair wants to merge 7 commits intoinventree:next-breakingfrom
matmair:refactor(backend)--restucture-user-endpoints

Conversation

@matmair
Copy link
Member

@matmair matmair commented Apr 28, 2025

This realigns the user API endpoints by:

  • moving endpoints that only return results for the current user to /user/me/
  • renaming the list endpoint for tokens from 'tokens' to 'token' as that name is now free

see #11433

@matmair matmair added api Relates to the API breaking Indicates a major update or change which breaks compatibility labels Apr 28, 2025
@matmair matmair added this to the 2.0.0 milestone Apr 28, 2025
@matmair matmair self-assigned this Apr 28, 2025
@netlify
Copy link

netlify bot commented Apr 28, 2025

Deploy Preview for inventree-web-pui-preview ready!

Name Link
🔨 Latest commit ca39264
🔍 Latest deploy log https://app.netlify.com/sites/inventree-web-pui-preview/deploys/680ff6eb261b5500083ea9ab
😎 Deploy Preview https://deploy-preview-9604--inventree-web-pui-preview.netlify.app
📱 Preview on mobile
Toggle QR Code...

QR Code

Use your smartphone camera to open QR code link.
Lighthouse
Lighthouse
1 paths audited
Performance: 95 (🔴 down 1 from production)
Accessibility: 89 (no change from production)
Best Practices: 100 (no change from production)
SEO: 78 (no change from production)
PWA: -
View the detailed breakdown and full score reports

To edit notification comments on pull requests, go to your Netlify site configuration.

@codecov
Copy link

codecov bot commented Apr 28, 2025

Codecov Report

✅ All modified and coverable lines are covered by tests.
⚠️ Please upload report for BASE (next-breaking@213f5a9). Learn more about missing BASE report.

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           
Flag Coverage Δ
backend 89.20% <100.00%> (?)

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

Components Coverage Δ
Backend Apps 91.69% <0.00%> (?)
Backend General 93.37% <0.00%> (?)
Frontend 70.81% <0.00%> (?)
🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

@matmair matmair changed the base branch from master to next-breaking February 26, 2026 20:01
@matmair matmair marked this pull request as ready for review February 27, 2026 00:18
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
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

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?

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

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

@matmair matmair marked this pull request as draft February 27, 2026 20:15
@matmair
Copy link
Member Author

matmair commented Feb 27, 2026

moving to draft while I think about the API change that was brought up

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

api Relates to the API breaking Indicates a major update or change which breaks compatibility

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants