Improvements #25
Labels
No Label
Compat/Breaking
Kind/Bug
Kind/Documentation
Kind/Enhancement
Kind/Feature
Kind/Security
Kind/Testing
Priority
Critical
Priority
High
Priority
Low
Priority
Medium
Reviewed
Confirmed
Reviewed
Duplicate
Reviewed
Invalid
Reviewed
Won't Fix
Status
Abandoned
Status
Blocked
Status
Need More Info
Unraid
No Milestone
No project
No Assignees
6 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: FrederikBaerentsen/BrickTracker#25
Loading…
Reference in New Issue
Block a user
No description provided.
Delete Branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Missing
as inventoryParts
as inventoryMinifigs
as inventoryWishlist
as inventoryParts
/parts
should keep table width/minifigs
add headline/minifigs
change table to grid and add theme selector / filter./wishlist
format table and add headline/config
add confirmation to delete databaseThanks for the awesome work so far! I have created a local install last week and started to import all my sets, love it!
2 improvements I would love to see;
Something else that could be a nice improvement is basic authentication. I would love to open up my instance so other people can view my list of stets but I don't want them to add or remove anything. I understand this is a lot more work but it could be a great improvement in the future.
Definitely a good idea. I'll add that.
It's something i want to implement. See #32. Hopefully sooner, rather than later.
I am not adding authentication, you can do that using basic auth in your reverse proxy or using authentik or authelia. It is too much to try and implement a proper authentication system. I use traefik with basic auth myself.
Not quite the same ask, but is there a plan for bulk add of sets (even just comma separated in the Add Set dialog), I have a lot to add and having to wait for the import to complete after each one makes it quite slow
I would love to see the option to automatically grab instruction pdf's from rebrickable or bricklink - perhaps not by default because some users wouldn't want them. Otherwise this is an awesome project and I look forward to continued development and improvements
A couple of features I'd like to see I'm currently using Koillection for mine but like the idea of how this breaks down individual components, any chance there's the possibility of adding in "Purchase Price", "Purchase Date", "Storage Location" or even if we could add our own check boxes that would be great, Thanks for putting in the time and effort to make this as good as it already is.
Also I like the idea of adding multiple sets at once (mainly for initial setup) and also grabbing the instructions as well.
This is unfortunately not possible. Rebrickable does not have instructions in their API. Brickset does, but it is a manual process of getting an API key with them, which complicates things.
This is a pretty good idea. I've also used Koillection before.
This is now implemented in v1.0.0.
@gregoo What's your thought on a search far or filter on the
parts
page and the parts section of thesets
page?There's already a search bar on the part page that searches in every applicable column.
For the part list in a set I did not use this library because it is made for pure data, and rewrites the rows when sorting the columns or searching, which breaks the field to update the number of missing part as well as the lightbox for the images.
To unbreak it you would require some post processing at every refresh which I believe is a lot of work for a section you won't consult a lot (and you can still search with the browser itself 😁)
I must be blind. I see the search bar now. That’s fair enough. You are right, the parts page probably isn’t used that much (there’s also a long loading time for the page).
Unfortunately all the pages load the entirety of entries.
The more sets you have, the more parts and minifigures you have and it can lead to sluggish loading times.
To have proper load time this would require paginating every query to the database. But that would require moving all of the search and logic to the database. My use case (< 200 sets from my youth 😁) doesn't require this kind of overhaul, but anyone can attempt it, that's the beauty of open source 😁.
I did a couple of tests with ~8000 rows and loading time is ~7s. Which is pretty acceptable. So i think we are good there.
Closed. See #52, as only export functionality remained.