FrederikBaerentsen/BrickTracker
5
10
Fork 6
Code Issues 12 Pull Requests 1 Actions Packages Projects 1 Releases 4 Wiki Activity

Since the original version of BrickTracker did not capture all fields, there should be a refresh button to refresh the data from #58

New Issue
Closed
opened 2025-01-28 22:38:07 +01:00 by gregoo · 5 comments
gregoo commented 2025-01-28 22:38:07 +01:00
Collaborator
Copy Link

Purposefully broken set:

image

Refreshing:

image

Refreshed:

image

🙂

Purposefully broken set: ![image](/attachments/7189fb2b-86e1-479d-8dc4-3e30b9be2353) Refreshing: ![image](/attachments/d79fdcad-baa7-4bba-8dda-226b55aa91fc) Refreshed: ![image](/attachments/5c0a12c4-9a7f-49a4-b340-4237d549ab42) 🙂
image.png
84 KiB
image.png
259 KiB
image.png
251 KiB
gregoo commented 2025-01-28 22:41:44 +01:00
Author
Collaborator
Copy Link

Another one with broken parts and minifigures

image
image

🥳

image
image

Another one with broken parts and minifigures ![image](/attachments/d05e204f-e759-42f4-9cc5-6fe402eb6475) ![image](/attachments/8e79677b-bab3-49a3-9c3c-68518e613a36) 🥳 ![image](/attachments/3961b60b-d916-49d2-96d4-6355d8f94585) ![image](/attachments/c48fe577-48f7-47e4-aa44-f635088e4a2d)
image.png
115 KiB
image.png
415 KiB
image.png
100 KiB
image.png
145 KiB
FrederikBaerentsen commented 2025-01-30 20:01:28 +01:00
Owner
Copy Link

Good idea. Haven't actually encountered this myself, but nice catch.

Good idea. Haven't actually encountered this myself, but nice catch.
gregoo commented 2025-01-31 15:51:47 +01:00
Author
Collaborator
Copy Link

You will definitely need it for the new part fields that were not captured from the API before (color RGB, transparency, print), and you may need it once again if you implement saving all the Brickset, BrickOwl, etc part number and color IDs 🙂

You will definitely need it for the new part fields that were not captured from the API before (color RGB, transparency, print), and you may need it once again if you implement saving all the Brickset, BrickOwl, etc part number and color IDs 🙂
gregoo commented 2025-02-04 23:02:40 +01:00
Author
Collaborator
Copy Link

Admin helper to list the sets that may need a refresh (no bulk tool planned)

image

image

Admin helper to list the sets that may need a refresh (no bulk tool planned) ![image](/attachments/2493fe53-dae1-4b37-8295-733a1d98df97) ![image](/attachments/3cbd8cf9-8039-4f7e-a780-bd749130253c)
image.png
16 KiB
image.png
121 KiB
gregoo commented 2025-02-10 16:48:28 +01:00
Author
Collaborator
Copy Link

Implemented in 1.2.0

Implemented in `1.2.0`
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
Compat/Breaking
Breaking change that won't be backward compatible
Kind/Bug
Something is not working
Kind/Documentation
Documentation changes
Kind/Enhancement
Improve existing functionality
Kind/Feature
New functionality
Kind/Security
This is security issue
Kind/Testing
Issue or pull request related to testing
Priority
Critical
The priority is critical
Priority
High
The priority is high
Priority
Low
The priority is low
Priority
Medium
The priority is medium
Reviewed
Confirmed
Issue has been confirmed
Reviewed
Duplicate
This issue or pull request already exists
Reviewed
Invalid
Invalid issue
Reviewed
Won't Fix
This issue won't be fixed
Status
Abandoned
Somebody has started to work on this but abandoned work
Status
Blocked
Something is blocking this issue or pull request
Status
Need More Info
Feedback is required to reproduce issue or to continue work
Unraid
Unsupported/Can't help
No Label
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
No Assignees
2 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: FrederikBaerentsen/BrickTracker#58
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?