Add support to run project submissions in frameworks like react, node, django etc.

Refer this pull request for the initial work that has been done. Create your PR against the project-worker branch

• Create project scenario
  • Complete setup method ( as done here in the test)
  • Complete run method
  • Complete result method
  • Write tests for the methods and scenario
• Run project job from queue
  • Accept following payload as input

   {
    "problem": <problem zip url>,
    "submission": <submission zip url>,
    "submissionDirs": <directories that can be editted>,
    "timelimit" <timelimit in seconds
  }
  

  • Send the payload to the job
• Refactor src/tasks/job.ts
  • Create src/tasks/jobs/ directory
  • Move all the jobs other than Base class to individual files in jobs dir
    Like move RunJob and its type to src/tasks/jobs/run.ts
  • Refactor imports to support current structure

The following documents are missing and should be added to validate the open source project and structure a community.

• Pull Request Template
• Issue Template
• Contributing Guidelines
• Code Of conduct

Working on it, claiming.

Version 10 of Node.js (code name Dubnium) has been released! 🎊

To see what happens to your code in Node.js 10, Greenkeeper has created a branch with the following changes:

• Added the new Node.js version to your .travis.yml
• Replaced the old Node.js version in your .nvmrc with the new one
• The engines config in 1 of your package.json files was updated to the new Node.js version

If you’re interested in upgrading this repo to Node.js 10, you can open a PR with these changes. Please note that this issue is just intended as a friendly reminder and the PR as a possible starting point for getting your code running on Node.js 10.

Your Greenkeeper Bot 🌴

note: this can be done only after part 1 of this is done
coding-blocks/judge-workers#3

Greenkeeper would discontinue its services by June 3rd, therefore we must migrate to Snyk, an alternative supported by Greenkeeper before the said date.

References:
https://greenkeeper.io/
https://snyk.io/

☝️ Important announcement: Greenkeeper will be saying goodbye 👋 and passing the torch to Snyk on June 3rd, 2020! Find out how to migrate to Snyk and more at greenkeeper.io

The devDependency @types/node was updated from 13.9.1 to 13.9.2.

🚨 View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

@types/node is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.

Your Greenkeeper Bot 🌴

☝️ Important announcement: Greenkeeper will be saying goodbye 👋 and passing the torch to Snyk on June 3rd, 2020! Find out how to migrate to Snyk and more at greenkeeper.io

The devDependency @types/shelljs was updated from 0.8.6 to 0.8.7.

🚨 View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

@types/shelljs is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.

Your Greenkeeper Bot 🌴

note: this can be done only after part 1 of this is done
coding-blocks/judge-workers#4

Since the judege-taskmaster codebase is used in production applications, the code needs to follow particular standards and guidelines, which can greatly increase its maintainability as a community project.

Therefore linters should be set up to force standard code guidelines on the repository.

Working on it, would send PR as soon as the issue acknowledged.

Test spec for Perl.
Inregards with issue coding-blocks/judge-workers#26

ProjectClass should be having submissionDirs.

Run spec for rust.
In regards with issue coding-blocks/judge-workers#32