Ticket #1301 (closed: fixed)
Create a FileProperty constructor that takes a single string
Reported by: | Peter Peterson | Owned by: | Peter Peterson |
---|---|---|---|
Priority: | minor | Milestone: | Iteration 24 |
Component: | Keywords: | ||
Cc: | Blocked By: | ||
Blocking: | Tester: | Michael Whitty |
Description
There should be another constructor in FileProperty that takes a single string rather than a vector<string> as many readers/writers only have a single extension to choose from.
Change History
comment:1 Changed 10 years ago by Peter Peterson
- Status changed from new to accepted
- Owner set to Peter Peterson
comment:3 Changed 10 years ago by Peter Peterson
- Status changed from accepted to closed
- Resolution set to fixed
comment:4 Changed 10 years ago by Peter Peterson
- Status changed from closed to reopened
- Resolution fixed deleted
Found a better way to solve the problem while working on ticket #1302. The FileValidator class does not need to be changed to do the right thing.
comment:6 Changed 10 years ago by Peter Peterson
- Status changed from accepted to closed
- Resolution set to fixed
comment:7 Changed 10 years ago by Nick Draper
- Status changed from closed to verify
moved to verify status
comment:9 Changed 10 years ago by Michael Whitty
- Status changed from verify to verifying
- Tester set to Michael Whitty
comment:10 Changed 10 years ago by Michael Whitty
- Status changed from verifying to closed
the constructor on FileProperty is overloaded to accept a single string rather than a vector of extensions. overloaded constructor has no unit test coverage
comment:11 Changed 5 years ago by Stuart Campbell
This ticket has been transferred to github issue 2148
Note: See
TracTickets for help on using
tickets.