Bug #693
Better sanity check for invalid BOM type
| Status: | Assigned | Start: | 10/02/2009 | |
|---|---|---|---|---|
| Priority: | Tabled | Due date: | ||
| Assigned to: | John Sexton | % Done: | 0% |
|
| Category: | Hardware | |||
| Target version: | - | |||
| Votes: | 0 |
Description
assert would be nice
History
Updated by John Sexton over 1 year ago
- Priority changed from Normal to Tabled
Updated by Kevin Woo over 1 year 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.
Updated by Alex Zirbel over 1 year ago
- Assigned to changed from Austin Buchan to John Sexton
Need to check if this issue was fixed.