…ect. Now, to get to the front end Angular code, you go to Angular/. To get to back end code, go to Express/. Adding new files all works the same, and the project compiles and operates like normal. Any questions, please ask Will. Also, now services are loaded through Express/Service/Services.js. Repositories are still referenced the same.
Cleaning - Went through all of the Express code, and cleaned it up. Look through previous code to see examples. Basically, the following rules are a MUST for all repo layer functions.
- Execute con.release() after finished using a connection. Not doing so will result in the server crashing when too many build up.
- Never catch a returned Promise, as this will prevent the service layer from handling a rejection. Rejections are key to determining
the success of a repo call.
…ect. Now, to get to the front end Angular code, you go to Angular/. To get to back end code, go to Express/. Adding new files all works the same, and the project compiles and operates like normal. Any questions, please ask Will. Also, now services are loaded through Express/Service/Services.js. Repositories are still referenced the same.
Cleaning - Went through all of the Express code, and cleaned it up. Look through previous code to see examples. Basically, the following rules are a MUST for all repo layer functions.