Challenge Overview
The Topcoder Github Launch Issue Button is a Chrome extension that can be used to launch a Topcoder challenge based on an issue in Github. The button is embedded on the Github page in Chrome and can be clicked to send the challenge out.
Currently, the mock we use for development, to translate the Github JSON into JSON that can be used to create a Topcoder challenge, is outdated. There is a new v3 Topcoder API available and this challenge will update the mock and its related tests to use the new API instead of what it currently uses.
Code:
The code for the mock can be found here:
https://github.com/cloudspokes/GLIB-mock
The V3 version of the Topcoder challenge API can be found here. Note the Swagger file that describes the service as that is a good entry point for the documentation of the services.
https://github.com/appirio-tech/ap-challenge-microservice .
A wrapper to the challenge service is available via NPM: https://www.npmjs.com/package/topcoder-api-challenges
The actual GLIB extension code is available here:
https://github.com/cloudspokes/GLIB-ChromeExt
Requirements:
A ticket is available here that comprises the overview of what we want to accomplish.
https://github.com/cloudspokes/GLIB-mock/issues/26
Tests
In addition to refactoring to use the new V3 Topcoder API, we also want to ensure that the existing tests are updated and pass as expected.
Heroku deployment
Heroku deployment is important so please ensure that the mock can be directly deployed to Heroku and make sure to document anything unexpected that might have to be done as part of the deploy.
Deployment guide
Your deployment guide needs to ensure that it covers not only deploying the mock, but how to validate using the Chrome Extension to ensure that the mock is working properly.
Video
No video is required for this challenge
Currently, the mock we use for development, to translate the Github JSON into JSON that can be used to create a Topcoder challenge, is outdated. There is a new v3 Topcoder API available and this challenge will update the mock and its related tests to use the new API instead of what it currently uses.
Code:
The code for the mock can be found here:
https://github.com/cloudspokes/GLIB-mock
The V3 version of the Topcoder challenge API can be found here. Note the Swagger file that describes the service as that is a good entry point for the documentation of the services.
https://github.com/appirio-tech/ap-challenge-microservice .
A wrapper to the challenge service is available via NPM: https://www.npmjs.com/package/topcoder-api-challenges
The actual GLIB extension code is available here:
https://github.com/cloudspokes/GLIB-ChromeExt
Requirements:
A ticket is available here that comprises the overview of what we want to accomplish.
https://github.com/cloudspokes/GLIB-mock/issues/26
Tests
In addition to refactoring to use the new V3 Topcoder API, we also want to ensure that the existing tests are updated and pass as expected.
Heroku deployment
Heroku deployment is important so please ensure that the mock can be directly deployed to Heroku and make sure to document anything unexpected that might have to be done as part of the deploy.
Deployment guide
Your deployment guide needs to ensure that it covers not only deploying the mock, but how to validate using the Chrome Extension to ensure that the mock is working properly.
Video
No video is required for this challenge