Introduction

In each of the sub-sections under this section, we will explain what code needs to be added to the generated application to develop the missing functionality and in which files the code needs to be added. Once this code is added, the timesheet application would function as in the final application demo.

Once the timesheet application is generated using the fastCode Application Generator, the developer can download the source code, open it in IDE, and make the necessary code changes to achieve the full business requirements.

The generated application provides a mechanism to add the additional functionality through extension classes. Currently it supports extending the back-end domain, application, and restcontrollers packages and the front-end account, admin, core, entities, and timesheeet-module modules.

Extending the generated application using these extension mechanisms allows us to update the application with data model changes without having to over-write the source code changes made by the developer to the generated application. This is accomplished by:

Re-generating only the classes in the core package in the back-end domain, application, and restcontrollers packages and the front-end account, admin, core, entities, and timesheeet-module modules and
Not touching the source code in the corresponding extension back-end packages and front-end modules.

NOTE: At this time, add-ons generated with the application, and other files in the back-end and the front-end, do not have extension mechanisms. In the near future, we intend to provide extension mechanisms for these files. Until then, during an update of the application, once the fastCode application generator does a git merge, the developer needs to manually resolve any Git merge conflicts in these files.