* fix(api): decouple api from curriculum This reverts commit8f0e441644
and introduces the implementations from #40703. * fix(gitpod): add curriculum build to GitPod This reverts commit706d70f58d
and introduces implementations from #41234. * docs: update DevOps manual for api change (#41259) Co-authored-by: Oliver Eyton-Williams <ojeytonwilliams@gmail.com>
21 lines
769 B
JavaScript
21 lines
769 B
JavaScript
import { flatten } from 'lodash';
|
|
|
|
// TODO: keeping curriculum in memory is handy if we want to field requests that
|
|
// need to 'query' the curriculum, but if we force the client to handle
|
|
// redirectToCurrentChallenge and, instead, only report the current challenge id
|
|
// via the user object, then we should *not* store this so it can be garbage
|
|
// collected.
|
|
|
|
import curriculum from '../../../../config/curriculum.json';
|
|
|
|
export function getChallenges() {
|
|
return Object.keys(curriculum)
|
|
.map(key => curriculum[key].blocks)
|
|
.reduce((challengeArray, superBlock) => {
|
|
const challengesForBlock = Object.keys(superBlock).map(
|
|
key => superBlock[key].challenges
|
|
);
|
|
return [...challengeArray, ...flatten(challengesForBlock)];
|
|
}, []);
|
|
}
|