* 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>
32 lines
1.1 KiB
JavaScript
32 lines
1.1 KiB
JavaScript
class ChallengeTitles {
|
|
constructor() {
|
|
this.knownTitles = [];
|
|
}
|
|
check(title, pathAndTitle) {
|
|
if (typeof title !== 'string') {
|
|
throw new Error(
|
|
`Expected a valid string for ${title}, but got a(n) ${typeof title}`
|
|
);
|
|
}
|
|
let titleToCheck = title.replace(/\s+/g, '').toLowerCase();
|
|
if (titleToCheck.length === 0) {
|
|
throw new Error('Expected a title length greater than 0');
|
|
}
|
|
// reassign titleToCheck if challenge is part of the project
|
|
// based curriculum
|
|
const isProjectCurriculumChallenge = title.match(/^Step\s*\d+$/);
|
|
titleToCheck = isProjectCurriculumChallenge ? pathAndTitle : titleToCheck;
|
|
const isKnown = this.knownTitles.includes(titleToCheck);
|
|
// TODO: check for the exceptions or remove the warning.
|
|
if (isKnown) {
|
|
console.warn(`
|
|
All current curriculum challenges must have a unique title.
|
|
The title ${title} (at ${pathAndTitle}) is already assigned
|
|
`);
|
|
}
|
|
this.knownTitles = [...this.knownTitles, titleToCheck];
|
|
}
|
|
}
|
|
|
|
module.exports = ChallengeTitles;
|