Actions
Feature #4288
closedMove sequence number file setting to the constructor
Start date:
Due date:
% Done:
100%
Estimated time:
Description
Currently the SequencingManager relies on Nlsr::initialize to be in a valid state regarding the path for its sequence number file. Instead, it should be done at constructor time, and not rely on an external function.
Updated by Nicholas Gordon about 7 years ago
- Target version changed from v0.4.0 to v0.5.0
Updated by Nicholas Gordon almost 7 years ago
- Target version changed from v0.5.0 to Minor release 0.4.1
Updated by Ashlesh Gawande almost 7 years ago
- Related to Task #1952: Decouple classes from Nlsr object for easier unit testing added
Updated by Nicholas Gordon almost 7 years ago
- Related to deleted (Task #1952: Decouple classes from Nlsr object for easier unit testing)
Updated by Nicholas Gordon almost 7 years ago
- Blocked by Task #1952: Decouple classes from Nlsr object for easier unit testing added
Updated by Ashlesh Gawande almost 7 years ago
- Target version changed from Minor release 0.4.1 to v0.5.0
Updated by Nicholas Gordon over 6 years ago
- Assignee deleted (
Nicholas Gordon)
This work should still be done. Unfortunately, the path of the file containing the sequence numbers is not set during ctor time, and that path is not available until Nlsr::initialize
. This means that this change would require a change in that class, too.
Updated by Ashlesh Gawande almost 6 years ago
- Status changed from New to Code review
- Assignee set to Ashlesh Gawande
Updated by Ashlesh Gawande almost 6 years ago
- Tracker changed from Task to Feature
- Status changed from Code review to Closed
- % Done changed from 0 to 100
Actions