[Codebase]: Separation of Concerns with R Packages #2
Labels
documentation
Improvements or additions to documentation
enhancement
New feature or request
question
Further information is requested
refactor
Code refactoring and cleanup
setup
Setup & Initialization
Ideally we want to have better separation of concerns with minimal coupling between the various components of the GMH project (i.e. Entrata API Interactions, R Shiny Modules, Authentication Plumber API, Database Management, Data Pipeline Orchestration, etc.).
Could split the codebase into separate self-contained, independent yet cohesive R packages if deem necessary. My initial instincts would be to split out:
gmhdatahub
)gmhentrata
)gmhauth
) - Note: should mergenoClocksAuthR
andnoClocksAuthPlumber
and remove unused code while refreshing underlying codeThe text was updated successfully, but these errors were encountered: