Price of 0 is treated as not having set a price. #153

New Issue

2026-04-19T04:19:12+02:00

commenter commented

2026-04-19 04:19:12 +02:00

Just a note, I'm noticing that sets/parts with a zero price assigned don't show a price later; it's as though they weren't assigned a price at all. I use this for gifts with purchases, etc, that didn't have an explicit cost.

I'll be checking out that 1.4.1 build sometime later on tomorrow.

Just a note, I'm noticing that sets/parts with a zero price assigned don't show a price later; it's as though they weren't assigned a price at all. I use this for gifts with purchases, etc, that didn't have an explicit cost. I'll be checking out that 1.4.1 build sometime later on tomorrow.

FrederikBaerentsen commented

2026-04-30 20:17:43 +02:00

Fixed in the upcoming 1.4.1 release. There were actually several places where 0 was being treated wrong (the badge display, the management input fields, the inline price editor, and the statistics range calculation).
All replaced with explicit None checks so $0.00 is treated as a real price throughout. Thanks for the report!

You can test it using the pre-1.4.1 docker tag.

Fixed in the upcoming 1.4.1 release. There were actually several places where 0 was being treated wrong (the badge display, the management input fields, the inline price editor, and the statistics range calculation). All replaced with explicit None checks so $0.00 is treated as a real price throughout. Thanks for the report! You can test it using the `pre-1.4.1` docker tag.

FrederikBaerentsen closed this issue

2026-04-30 20:17:43 +02:00

FrederikBaerentsen added the Kind/Bug label 2026-04-30 20:18:05 +02:00

commenter commented

2026-05-01 19:24:23 +02:00

Confirmed fixed!

Sign in to join this conversation.

2 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: FrederikBaerentsen/BrickTracker#153