[FR]Hide non-relevant fields for virtual parts
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 66/100
Research direction
Find the part edit form or component that renders the Default location and minimum/maximum stock inputs, then read how it identifies virtual parts. Hide those fields for virtual parts and check the form for both virtual and non-virtual parts to confirm the fields appear only where applicable.
Written by the indexing model from the issue text.
Description
Please verify that this feature request has NOT been suggested before.
- I checked and didn't find a similar feature request
Problem statement
The following fields are not applicable for virtual parts:
- Default location
- Minimum/maximum stock
I think hiding these inputs for virtual part makes sense
Suggested solution
Hide those inputs
Describe alternatives you've considered
Make them at least disabled
Examples of other systems
Do you want to develop this?
- I want to develop this.
- Dominant language
- Python
- Stars
- 7.7k
- Forks
- 1.6k
- Avg merge
- 21h 45m
- Merged PRs (30d)
- 204
Getting set up
Starts the project's dev container in your browser, under your own GitHub account.
- No Dockerfile or Docker Compose file
- No pull request template
- Read the contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from inventree/InvenTree
-
enhancement User Interface wontfix
Difficulty 2/5 1-3 hours Newbie friendliness 67/100
inventree/InvenTree#13292 · 5 comments ·
Maintainers usually reply within 1 day
-
[FR] Add spinner arrows in Quantity when adding a BOM itemMay be free again @Alonso-Lopez-1 claimed this 50 days ago, and no pull request is open. Openenhancement help wanted starter User Interface
Difficulty 2/5 1-3 hours Newbie friendliness 61/100
inventree/InvenTree#12677 · 6 comments ·
Maintainers usually reply within 1 day
-
enhancement triage:not-checked
Difficulty 2/5 1-3 hours Newbie friendliness 58/100
inventree/InvenTree#13317 · 1 reaction ·
Maintainers usually reply within 1 day
-
bug stock
Difficulty 3/5 1-2 days Newbie friendliness 40/100
inventree/InvenTree#13285 · 1 comment ·
Maintainers usually reply within 1 day
-
Functional reorganisation of backend codebasePossibly taken A pull request linked to this issue is open or already merged. Open
Difficulty 5/5 Over a week Newbie friendliness 20/100
Maintainers usually reply within 1 day
All issues in inventree/InvenTree
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
ip-tools/patzilla#219 · 2 comments ·
Maintainers usually reply within 1 day
-
EPSSClient commits to its SQLite cache once per score: a 100-CVE bulk fetch makes 101 disk flushesOpenpriority:p3 technical-debt
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
jimmy058910/jmo-security-repo#1673 ·
Maintainers usually reply within 1 day
-
enhancement ready
Difficulty 2/5 1-3 hours Newbie friendliness 86/100
-
integration: frontier_silicon
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
home-assistant/core#193176 · 2 comments ·
Maintainers usually reply within 1 day
-
task create and task update take --body-file and --stdinPossibly taken @JuanBarriosS claimed this today. Opencli enhancement good first issue help wanted
Difficulty 2/5 1-3 hours Newbie friendliness 92/100
pyrite-wiki/pyrite#1687 · 1 comment ·
Maintainers usually reply within 1 day