File system class for use in the parser. #19

Closed
opened 2025-10-17 12:09:02 -07:00 by azpect · 1 comment
Owner

Currently, the parser handles file I/O, which does not meet the OOP principle of single responsibility classes. To resolve this violation, a FileSystem class will be implemented.

This class will be constructed wth a required string for the input file, and an optional string for the output. The class will have methods such as readInput and writeOutput. The class will abstract all filesystem operations.

Eventually, the watchdog class will utilize this module. But this implementation will not have that functionality. Once this issue is complete, it will be passed to @shultzp1 to complete the watchdog implementation.

Currently, the `parser` handles file I/O, which does not meet the OOP principle of **single responsibility classes**. To resolve this violation, a `FileSystem` class will be implemented. This class will be constructed wth a required string for the input file, and an optional string for the output. The class will have methods such as readInput and writeOutput. The class will abstract all filesystem operations. Eventually, the `watchdog` class will utilize this module. But this implementation will not have that functionality. Once this issue is complete, it will be passed to @shultzp1 to complete the watchdog implementation.
azpect added the
Kind/Enhancement
Priority
Medium
labels 2025-10-17 12:09:02 -07:00
azpect self-assigned this 2025-10-17 12:09:02 -07:00
azpect added this to the (SPRINT) Parser creation project 2025-10-17 12:09:02 -07:00
azpect moved this to In Progress in (SPRINT) Parser creation on 2025-10-17 13:20:04 -07:00
azpect moved this to Done in (SPRINT) Parser creation on 2025-10-20 12:06:55 -07:00
Author
Owner

Close with the merging of #20 .

Close with the merging of #20 .
Sign in to join this conversation.
No description provided.