Challenge Overview

Using the previous build system and the output from previous FF GAS challenges, port over the existing application to use the current build system. All features from the original plug-in should be ported over to Angular and Ionic (use the output from the POC). It should use JSForce to interact with the SF API. All code should be fully unit tested. All of the Jquery based functionality should be ported over to use Angular (and lodash) native functions as much as possible. Please document all code. It should be fully functional with both Google Sheet and MS Office 365 Excel.

Migrate all the operations from the SOQL builder to use the traverser and the codegenerator. Testing can be done using the parser as a validator (no tree means validation failed). It's recommend to use one of the following to interact with the SF API (ideally the Angular libraries ngForce or forceng):

 

 

You'll need access to the following repo's. Apply for access in the forums:

 

  • - New build system and test set up created with Gulp

  • - Parser code base (the data for the tests can be used as dummy data for your own tests)

  • - AST walker code base

  • - SOQL code generator

  • - Ionic decorator for Angular Schema Form

  • -The original (legacy) FF GAS app

  • The code base from the FF GAS O365 POC

Deliverables

  • - A fully functioning app with the original features ported over to work in Angular and Ionic (as per the FF GAS O365 POC)

  • - Use the new build system to create tested and working deployment assets for Google App Script in Google Sheets and O365.

  • - Migrate operations from the original SOQL builder to use the traverser, AST walker and SOQL code generator

  • - Use the Ionic Angular Schema Form decorator to auto generate forms from existing SF reports

Resources

Repo/Housekeeping

  • - You will need to base your work off the git repositories provided.

  • - You will be required to handle any merge issues that occur from your submission.

Coding Standards

  • - All code should be fully unit tested and documented. Please use best practise here (you do not need to document getters and setters, etc)!

  • - All existing tests should be fully maintained (ie if you make a change to the existing functionality that breaks a test you need to fix that).



Final Submission Guidelines

- Please provide a detailed deployment guide in Word format with screenshots - walking through all the installation and verification

- Provide a demo video walking through the installation and verification.

- Provide all your source code as a zip

ELIGIBLE EVENTS:

2016 TopCoder(R) Open

Review style

Final Review

Community Review Board

Approval

User Sign-Off

ID: 30053849