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
Currently, we have multiple functions responsible for formatting scripts for various purposes, such as inspecting script contents or displaying them in the script or output windows. These functionalities have significant overlap but are implemented across different classes.
To improve maintainability and adhere to the DRY (Don't Repeat Yourself) principle, I propose consolidating these implementations into a single class or a cohesive set of related classes. This will streamline the functionality and make the codebase easier to manage and extend.
The text was updated successfully, but these errors were encountered:
Thanks @Patowhiz , I am adding @lilyclements into this thread. We now have documentation on the R-Instat "packages", i.e. on all the special functions we have been producing. (Note the "Royal we" here, because I haven't produced any myself.)
We have a plan to make use of the packages - rather than each individual function separately - as soon as possible. Your suggestion is relevant here.
Currently, we have multiple functions responsible for formatting scripts for various purposes, such as inspecting script contents or displaying them in the script or output windows. These functionalities have significant overlap but are implemented across different classes.
To improve maintainability and adhere to the DRY (Don't Repeat Yourself) principle, I propose consolidating these implementations into a single class or a cohesive set of related classes. This will streamline the functionality and make the codebase easier to manage and extend.
The text was updated successfully, but these errors were encountered: