8614db7a32
* feat: use legacy flag chore: reorder challenges fix: linter revert: server change feat: unblock new editor fix: proper order fix: 0-based order fix: broke the order feat: move tribute certification to its own block feat: split the old projects block into 4 fix: put all blocks in order chore: add intro text refactor: use block, not blockName in query fix: project progress indicator * fix: reorder new challenges/certs * fix: reorder legacy challenges * fix: reintroduce legacy certs * feat: add showNewCurriculum flag to env * chore: forgot sample.env * feat: use feature flag for display * fix: rename meta + dirs to match new blocks * fix: add new blocks to help-category-map * fix: update completion-modal for new GQL schema * test: duplicate title/id errors -> warnings * fix: update completion-modal to new GQL schema Mk2 * chore: re-order metas (again) * fix: revert super-block-intro changes The intro needs to show both legacy and new content. We need to decide which pages are created, rather than than what a page shows when rendered. * feat: move upcoming curriculum into own superblock * fix: handle one certification with two superBlocks * fix: remove duplicated intros * fix: remove duplicate projects from /settings * fix: drop 'two' from Responsive Web Design Two * chore: rename slug suffix from two to v2 * feat: control display of new curriculum * feat: control project paths shown on /settings * fix: use new project order for /settings This does mean that /settings will change before the release, but I don't think it's serious. All the projects are there, just not in the legacy order. * fix: claim/show cert button * chore: remove isLegacy Since we have legacy superblocks, we don't currently need individual blocks to be legacy * test: fix utils.test * fix: verifyCanClaim needs certification If Shaun removes the cert claim cards, maybe we can remove this entirely * fix: add hasEditableBoundaries flags where needed * chore: remove isUpcomingChange * chore: v2 -> 22 Co-authored-by: Oliver Eyton-Williams <ojeytonwilliams@gmail.com>
95 lines
2.1 KiB
JavaScript
95 lines
2.1 KiB
JavaScript
const html = 0;
|
|
const js = 1;
|
|
const backend = 2;
|
|
const zipline = 3;
|
|
const frontEndProject = 3;
|
|
const backEndProject = 4;
|
|
const bonfire = 5;
|
|
const modern = 6;
|
|
const step = 7;
|
|
const quiz = 8;
|
|
const invalid = 9;
|
|
const pythonProject = 10;
|
|
const video = 11;
|
|
const codeally = 12;
|
|
|
|
// individual exports
|
|
exports.backend = backend;
|
|
exports.frontEndProject = frontEndProject;
|
|
exports.backEndProject = backEndProject;
|
|
exports.pythonProject = pythonProject;
|
|
|
|
exports.challengeTypes = {
|
|
html,
|
|
js,
|
|
backend,
|
|
zipline,
|
|
frontEndProject,
|
|
backEndProject,
|
|
pythonProject,
|
|
bonfire,
|
|
modern,
|
|
step,
|
|
quiz,
|
|
invalid,
|
|
video,
|
|
codeally
|
|
};
|
|
|
|
// (Oliver) I don't think we need this for codeally projects, so they're ignored
|
|
// here
|
|
exports.isProject = challengeType => {
|
|
if (typeof challengeType !== 'number')
|
|
throw Error('challengeType must be a number');
|
|
return (
|
|
challengeType === frontEndProject ||
|
|
challengeType === backEndProject ||
|
|
challengeType === pythonProject
|
|
);
|
|
};
|
|
|
|
// turn challengeType to file ext
|
|
exports.pathsMap = {
|
|
[html]: 'html',
|
|
[js]: 'js',
|
|
[bonfire]: 'js'
|
|
};
|
|
// determine the component to view for each challenge
|
|
exports.viewTypes = {
|
|
[html]: 'classic',
|
|
[js]: 'classic',
|
|
[bonfire]: 'classic',
|
|
[frontEndProject]: 'frontend',
|
|
[backEndProject]: 'backend',
|
|
[pythonProject]: 'frontend',
|
|
[modern]: 'modern',
|
|
[step]: 'step',
|
|
[quiz]: 'quiz',
|
|
[backend]: 'backend',
|
|
[video]: 'video',
|
|
[codeally]: 'codeally'
|
|
};
|
|
|
|
// determine the type of submit function to use for the challenge on completion
|
|
exports.submitTypes = {
|
|
[html]: 'tests',
|
|
[js]: 'tests',
|
|
[bonfire]: 'tests',
|
|
// requires just a single url
|
|
// like codepen.com/my-project
|
|
[frontEndProject]: 'project.frontEnd',
|
|
// requires two urls
|
|
// a hosted URL where the app is running live
|
|
// project code url like GitHub
|
|
[backEndProject]: 'project.backEnd',
|
|
[pythonProject]: 'project.backEnd',
|
|
[step]: 'step',
|
|
[quiz]: 'quiz',
|
|
[backend]: 'backend',
|
|
[modern]: 'tests',
|
|
[video]: 'tests'
|
|
};
|
|
|
|
// determine which help forum questions should be posted to
|
|
exports.helpCategoryMap = require('./help-category-map.json');
|