-
-
Notifications
You must be signed in to change notification settings - Fork 669
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Feature/Tree picker #5595
Feature/Tree picker #5595
Conversation
✅ Deploy Preview for inventree ready!
To edit notification comments on pull requests, go to your Netlify site configuration. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Lgtm; the inclusion of the structural field warrants an API version bump
You're right, missed that, added it now. |
@wolflu05 sorry for the delayed response on this one - it looks fantastic! No notes :) |
Thanks that you like this. To build this in PUI, I think it would be better to build the tree component first. From my research, we could use this library which is unsing virtualization what drastically improves performance on large data sets. They show an example with 1848897 nodes and the performance is awesome. |
This bothered me since a long time. It is very hard if one has locations with the same repeating name to search for them by a tree path. To improve the experience I added a tree picker to the forms which shows the tree in a new modal to select the correct path. Additionally, this improves the backdrop for secondary, ... modals, so that only the top modal is infront of the backdrop.
inventree-tree-picker.mp4
This could have some performance issues like the top navigation has them too, but this is related to the jQuery tree view library. I hope we can implement something like this in PUI sometime too. But for now this PR is ready to review.