Hi every, thank you for taking the time to visit this thread. Here is the background, I am wanting to eventually start my own software development company and right now I have secured a contract job to build out a ticket maintenance system for an offshore company. What I'm wanting to do is develop a base stack so that I can use it going forward on future projects.
I have written a simple console application that takes the following arguments so that it automatically generates the code that I'm displaying below:
In my next several posts, I will provide the code that I am currently using to represent my Menu table in my database.
For visibility, this is what the file structure looks like:
What I am hoping to achieve is direction on:
I have written a simple console application that takes the following arguments so that it automatically generates the code that I'm displaying below:
- Table name
- Column names
- File type (model, database, service, api)
In my next several posts, I will provide the code that I am currently using to represent my Menu table in my database.
For visibility, this is what the file structure looks like:
Code:
root
├── pages
├── server
│ ├── api
│ ├── database
│ ├── model
│ ├── service
│ └── utilities
└── vendor- Does this code structure make sense to other developers. I.e. if you were to inherit this project with no knowledge of who I am or how the project was developed, would it take too much effor to maintain
- Can the code be simplified?
- What suggestions do y'all have?
