Started using fw/1 in a legacy app, which has abou...
# fw1
a
Started using fw/1 in a legacy app, which has about 20 subdirs under the root. Right now, it’s working nicely in 1 of those subdirs, with an app.cfc in the subdir. As I expand the usage of fw/1 gradually to other areas of the app (to other sub dirs), any recommendations on how to do that. I could do what I did before, but that will end up with multiple subdirs with their own app.cfc and fw/1 instances. Should I be looking at subsystems instead? Or maybe just implement at the root with all the legacy subdirs in unhandledPath list, until I get to convert them? Thanks
c
I'd probably go the
unhandledPath
approach to start with. As far as code organization goes, as you move each subdirectory to FW/1, could all the stuff in that subdirectory be handled by only one controller or just a few controllers"? Is there discreet business logic (models) contained with that subdirectory? Does the functionality in that subdirectory stand alone from the main application? The answers to those questions should guide you whether to use subsystems or not.
🙌 1