Vue (pronounced /vjuː/, like view) is a progressive framework for building user interfaces. It is heavily utilized in the report to update the information in the various views dynamically. (Style guide available here, Developer tool available here). Vue lifecycle hooks are the defined methods that get executed in a particular stage of the Vue object lifespan. The following is the Vue lifecycle diagram taken from here indicating the hook sequence:
The main Vue object (
app.vue) is responsible for loading the report via an async call to
api.js, which parses
repos attribute is tied to the global
window.REPOS, and is passed into the various other modules when the information is needed.
The report interface is broken down into two main parts
The summary view acts as the main report, which shows the various calculations.
The tabbed interface is responsible for loading various modules such as authorship and zoom to display additional information.
This contains the logic for the main VueJS object,
app.vue, which is the entry point for the web application.
store.js is used to pass the necessary data into the relevant modules.
v_ramp are components embedded into the report and will render the corresponding content based on the data passed into it from Vuex.
The main Vue object depends on the
summary.json data to determine the right
commits.json files to load into memory. This is handled by
api.js, which loads the relevant file information from the network files if available; otherwise, a report archive,
archive.zip, has to be used.
Once the relevant
commit.json files are loaded, all the repo information will be passed into
v_summary to be loaded in the summary view as the relevant ramp charts.
Most activity or actions should happen within the module itself, but in the case where there is a need to spawn or alter the view of another module, an event is emitted from the first module to the Vuex store, which then handles the data received and passes it along to the relevant modules.
Other than the global main Vue object, another global variable we have is the
window.hashParams. This object is responsible for generating the relevant permalink for a specific view of the report's summary module.
This is the module that is in charge of loading and parsing the data files generated as part of the report.
Due to security design, most modern browsers (e.g., Chrome) do not allow web pages to obtain local files using the directory alone. As such, a ZIP archive of the report information will be produced alongside the report generation.
This archive will be used in place of the network files to load information into the report when the network files are unavailable.
The API module will be handling all requests for all the JSON data files. If the network file is not available, the files will be obtained from the zip archive provided.
After the JSON files are loaded from their respective sources, the data will be parsed as objects and included inside the global storage object,
window.REPOS, in the right format.
For the basic skeleton of
window.REPOS, refer to the generated
summary.json file in the report for more details.
v_summary module is in charge of loading the ramp charts from the corresponding
The summary module is activated after the information is loaded from the main Vue.JS object. At creation, the
repo attribute is populated with the
window.REPOS object, which contains information loaded from
The commits information is retrieved from the corresponding project folders for each repository. This information will be filtered and sorted before being passed into the template to be displayed as ramp charts.
The authorship module retrieves the relevant information from the corresponding
authorship.json file if it is not yet loaded. If it has been loaded, the data will be written into
window.REPOS and be read from there instead.
The files will be filtered, picking only files the selected author has written in. The lines are then split into chunks of "touched" and "untouched" code segments displayed in the tab view which will be popped up on the right side of the screen.
v_zoom module is in charge of filtering and displaying the commits from the ramp chart's selected sub-range.
v_ramp module is responsible for receiving the relevant information from
v_summary and generating ramp charts that contain ramp slices.
For ramps between the date ranges, the slices will be selected and it will be pre and post padded with empty slices to align the ramp slice between the
untilDate. The ramps will then be rendered with the slices in the right position.
v-segment module is used as a component in
v_authorship. It separates the code in terms of "touched" and "untouched" segments and only loads each "untouched" segment when it is toggled.