Hey @DJ Wolfson ,
How are you handling the organization of files under the "server" folder?
Just like you, I've been trying to figure out the best file structure and came across this thread.
I have the following simple app created so far:
So, trying to follow the structure proposed in this post and if my understanding is correct, now.ts files should define the metadata and in these files is where we would import some JS file containing our business logic, but how would you organize this under your server folder?
In a real project you can have multiple tables, each with multiple configurations such as BRs, UI Policies, Client Scripts, etc.
I've been struggling to find information about the best practices on organizing the files of a fluent project, and it is understandable as it is new feature.
I have many questions and ideas, but here are two important ones I'd like to clarify.
Having some feedback about this question could really help me to figure out some other stuff I'm thinking about.
- If I want to add some business rules to my table "Menu Item", should all the BRs be defined on the menu_item > business_rules.now.ts file?
Or is it better to create a folder called "business rules" and in there put individual files where each define one business rule? Example: menu_item > business_rules > first_business_rule.now.ts - So, regarding the logic of the business rule, how should it be organized under the "server" file?
Is the structure from my image close to the recommended practice?
Or should we use a similar approach to fluent folder? i.e: create a table name folder and then put all the related files inside? Example: server > menu_item > business_rules > first_business_rule.js
I guess one of my concerns with putting the business logic into individual files is the naming. Generally, one names business rules describing what is the action being performed and that can get a little verbose. In my experience I haven't seen a file named like: server > business_rules > menu_item > validate_menu_item_on_insert.js
That's more like a function name, not a file.
Another way, to mitigate that could be to put the business logic into entities/classes, then refer to those classes from the now.ts files.
Or I can be in the wrong direction, and in reality, the recommended best practice can be that we put the business logic directly into the BR definition file (now.ts).
I know this can be worked out in different ways and I don't expect you to answer my questions/concerns as you will probably be in the same is spot as I am or you may have figured this out already.
I'd love to see someone else's fluent projects to kind of get an idea of the file structure/organization.
Thanks!
