Challenge Overview
Description:
For this challenge we will be updating the GLIB-mock node service that is used by the GLIB-Chrome Extension to create challenges. We will be updating the challenge creation service to support populating the Submission guidelines in a challenge based on the markdown provided. Also we will be pulling the URL of the repository for the challenge from the markdown and including it in the challenge.
Requirements:
- Update the code that processes the markdown to properly find the submission guidelines and repository URL.
Update the call to create the challenge to include the submission guidelines including the repository location.
The Submission Guidelines should not be included in the Detailed requirements.
If the ### Submissions: header is not found the following default value should be used:- Ensure good test coverage on all modules
Upload documentation for how to run your submission
Upload all your source code as a zip for review
Winner will be required to submit a pull request with their winning code.
Update the Submission Guidelines payload to include the following text - Ensure good test coverage on all modules
The repository for this challenge can be found [here](REPOSITORY).
Where the REPOSITORY value is the url read from the markdown provided. If no repository is found the line will not be included.
Setup & Reference:
- Fork this repository and work off this branch.
The data to populate the Submission Guidelines field can be found in the markdown under after the### Submissions: header until the end of the document or another header element is found. Seethis template for reference.
The repository for the challenge will be provided under the ### Repository: markdown
The property key used to set for the submission guidelines is submission.
See the forum for auth information.
Final Submission Guidelines
Submissions:
- Ensure good test coverage on all modules
Upload documentation for how to run your submission
Upload all your source code as a zip for review
Add lazybaer and gbockus as members of your forked repository
Winner will be required to submit a pull request with their winning code.