trimming

[bps-github7]

general refactoring efforts:

• Eliminate packaging syntax.
• Eliminate random code bloat.
  • unused import statements
  • modules which could be combined
  • functions that could be turned into imperative statement.
  • make sure you comprehend the process fully to avoid repeating functionality.

organization

We need a very clear idea of how all use cases are implemented, as well as how data flows through the program
specifically, what type of data structure contains 's data, and what properties and behaviors does
it have at a certain point.

however, ive neglected the obvious in the past

• use case diagram
• sequence diagram
• class diagram

I've avoided doing this in the past because it is intutive and rather self explanatory

• input is passed back to the program as a str
• its broken down into separate Inline (one per file) object.
• we get a list of multiple inline objects in most cases, that would be multiple lines of input, delimited by newline or carriage return.

then we simply loop over the list and run the generator function to generate the files. Should validation be applied, this
would change the properties of the Inline object dynamically, after it has been generated.

error handling

program should be able to recognize and stop itself should it be about to encounter bad input
when user or code generated errors are thrown, gracefully handle them and crash the program only when necessary

• need more try except
• raise exceptions either predefined or custom made for file generator