• HOME
  • SHOWCASE
  • USER GUIDE
  • DEVELOPER GUIDE
  • ABOUT
  • CONTACT
  • You are looking at the developer documentation for the most recent public release of RepoSense. The version matching the latest master branch is here.

    HTML report

    The source files for the report is located in frontend/src and is built by spuild before being packaged into the JAR file to be extracted as part of the report.

    The main HTML file is generated from frontend/src/index.pug.

    Vue (pronounced /vjuː/, like view) is a progressive framework for building user interfaces. It is heavily utilized in the report to dynamically update the information in the various views. (Style guide available here, Developer tool available here). Vue lifecycle hooks are the defined methods which gets executed in a certain stage of the Vue object lifespan. The following is the Vue lifecycle diagram taken from here indicating the hook sequence:

    The following is a snapshot of the report:

    Report architecture

    The main Vue object (window.app) is responsible for the loading of the report (through summary.json). Its repos attribute is tied to the global window.REPOS, and is passed into the various other modules when the information is needed.

    window.app is broken down into two main parts

    • the summary view
    • and the tabbed interface

    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.

    Javascript files

    • main.js - main controller that pushes content into different modules
    • api.js - loading and parsing of the report content
    • v_summary.js - module that supports the summary view
    • v_authorship.js - module that supports the authorship tab view
    • v_zoom.js - module that supports the zoom tab view
    • v_ramp.js - module that supports the ramp chart view
    • v_segment.js - module that supports the code segment view

    JSON Report files

    • summary.json - a list of all the repositories and their respective details
    • projName/commits.json - contains information of the users' commits information (e.g. line deletion, insertion, etc), grouped by date
    • projName/authorship.json - contains information from git blame, detailing the author of each line for all the processed files

    Main (main.js)

    This contains the logic for main VueJS object, window.app, which is responsible for passing the necessary data into the relevant modules to be loaded.

    v_summary, v_authorship, v_zoom, v_segment and v_ramp are components which will be embedded into report and will render the corresponding content based on the data passed into it from the main window.app.

    Loading of report information

    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 it is available, otherwise a report archive, archive.zip, have 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.

    Activating additional view modules

    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 main Vue object (window.app), 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 reponsible for generating the relevant permalink for a specific view of the summary module for the report.

    Data loader (api.js)

    This is the module that is in charge of loading and parsing the data files generated as part of the report.

    Loading from ZIP file

    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, in the case when the network files are unavailable.

    The API module will be handling all request for all the JSON data files. If the network file is not available, the files will be obtained from the zip archive provided.

    Retrieving and parsing information

    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.

    Summary view (v_summary.js)

    The v_summary module is in charge of loading the ramp charts from the corresponding commits.json.

    Initializing the data for the ramp charts

    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 summary.json.

    Filtering users and repositories

    The commits information is retrieved from the corresponding project folders for each repository. These information will be filtered and sorted before passed into the template to be displayed as ramp charts.

    Authorship view (v_authorship.js)

    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.

    Showing relevant information by authors

    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 to be displayed in the tab view which will be popped up on the right side of the screen.

    Zoom view (v_zoom.js)

    The v_zoom module is in charge of filtering and displaying the commits from selected sub-range of a ramp chart.

    Ramp view (v_ramp.js)

    The v_ramp module is responsible for receiving the relevant information from v_summary and generating ramp charts that contain ramp slices.

    Padding for dates

    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 sinceDate and untilDate. The ramps will then be rendered with the slices in the right position.

    Segment view (v_segment.js)

    The 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.