Closed SchrodingersGat closed 2 days ago
Name | Link |
---|---|
Latest commit | afb0f2f63f1190bcd4ff847350e5ef59f45f14ef |
Latest deploy log | https://app.netlify.com/sites/inventree-web-pui-preview/deploys/673cf9f9e470220009760275 |
Deploy Preview | https://deploy-preview-8524--inventree-web-pui-preview.netlify.app |
Preview on mobile | Toggle QR Code...Use your smartphone camera to open QR code link. |
Lighthouse |
1 paths audited Performance: 100 (π’ up 1 from production) Accessibility: 86 (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.
Attention: Patch coverage is 77.77778%
with 6 lines
in your changes missing coverage. Please review.
Project coverage is 84.63%. Comparing base (
2bc6ddb
) to head (afb0f2f
). Report is 4 commits behind head on master.
Files with missing lines | Patch % | Lines |
---|---|---|
src/backend/InvenTree/part/api.py | 76.47% | 4 Missing :warning: |
src/frontend/src/tables/part/RelatedPartTable.tsx | 33.33% | 2 Missing :warning: |
:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.
π¨ Try these New Features:
We might could also overengineer this by adding a second table like relation types which can be selected. That way we can keep this field much clear/filter/β¦ by common relations types. E.g. show all additional equipment relations, β¦ But thatβs just a thought
Using a state would probably be user-friendly as custom states would make it easy to extend the selection without adding new interfaces that need management functionality and discovery. That could be added as a separate PR to keep this one in the imminent 0.17.0
Using a state would probably be user-friendly as custom states would make it easy to extend the selection without adding new interfaces that need management functionality and discovery. That could be added as a separate PR to keep this one in the imminent 0.17.0
@matmair should we create an issue to track this then? Maybe you could do that with you ideas about the custom states? I'm not so familiar with the new state system.