You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The fiscal_impact script currently has a miscellaneous section and a section A that are mostly initialization steps (confirm working directory, calculate current date, etc). As the script currently stands, they constitute lines 1 - 65.
It's up to our discretion to determine what should be in the main fiscal_impact script and what should be in a separate one, but I definitely think it would be helpful to at least have configuration steps - like the working directory setup and loading packages - in a different script. Preferably, we set up the project environment so it automatically loads. Likely, we'll end up with some sort of configuration script and keep some of the functionality from the "miscellaneous" and section A of the FIM in the main fiscal_impact script.
Thus, doing this task requires a few steps:
understanding what the "miscellaneous" and Section A do and determining which lines of code should be transferred to a different script
Determining whether the project already has a configuration script/environment
Creating a new config script or adding relevant code to existing script
Refactoring the code so it is cleaner.
This is a larger task and might better be split up into separate issues once we have a better grasp of the situation.
The text was updated successfully, but these errors were encountered:
The fiscal_impact script currently has a miscellaneous section and a section A that are mostly initialization steps (confirm working directory, calculate current date, etc). As the script currently stands, they constitute lines 1 - 65.
It's up to our discretion to determine what should be in the main fiscal_impact script and what should be in a separate one, but I definitely think it would be helpful to at least have configuration steps - like the working directory setup and loading packages - in a different script. Preferably, we set up the project environment so it automatically loads. Likely, we'll end up with some sort of configuration script and keep some of the functionality from the "miscellaneous" and section A of the FIM in the main fiscal_impact script.
Thus, doing this task requires a few steps:
This is a larger task and might better be split up into separate issues once we have a better grasp of the situation.
The text was updated successfully, but these errors were encountered: