Bug #693
Better sanity check for invalid BOM type
Start date:
10/02/2009
Due date:
% Done:
0%
Description
assert would be nice
History
#1 Updated by John Sexton over 12 years ago
Kevin/Austin what does this mean?
#2 Updated by John Sexton over 12 years ago
- Priority changed from Normal to Tabled
#3 Updated by Kevin Woo over 12 years ago
When initializing the BOM, either as an 1.0 or 1.5 there isn't a good check.
Ie: I could put like 4 or something like that (I don't remember the
specifics of how the version are represented). Basically you should make
sure it's one of those versions and not some number someone made up.
#4 Updated by Alex Zirbel over 12 years ago
- Assignee changed from Austin Buchan to John Sexton
Need to check if this issue was fixed.