"Required to complete" feature

[LukaszGrela]

This adds ability to specify which components should be completed to mark entire block (and other components) as completed. Block model needs to specify _requireCompletionOf property which can have following values: 'all', 'any' or valid component id that is child of this block e.g. c-02. Below are few examples of use. When _requireCompletionOf is missing or empty it defaults to all.

{
    "_id": "b-03",
    "_parentId": "a-02",
    "_type": "block",
    "_requireCompletionOf": "any"
},
{
    "_id": "b-03",
    "_parentId": "a-02",
    "_type": "block",
    "_requireCompletionOf": ["all"]
},
{
    "_id": "b-03",
    "_parentId": "a-02",
    "_type": "block",
    "_requireCompletionOf": "c-05"
},
{
    "_id": "b-03",
    "_parentId": "a-02",
    "_type": "block",
    "_requireCompletionOf": ["c-05","c-10"]
},

[brian-learningpool]

Lukasz, there has been some discussion around the area of what counts towards completion in issue #490.

I think that a better approach might be for components to say whether or not they require completion to be counted as part of the course completion.

[LukaszGrela]

Maybe, but this way I found it less invasive, it will work with previous and future sources.

[oliverfoster]

Note: Current isOptional proposals do not provide Lukasz 'any' functionality which could be quite useful.

[taylortom]

Can see the use for the completion of any - will park this for when we tackle the _isOptional implementation

[moloko]

@LukaszGrela - as we mentioned we have been working on implementing the _isOptional feature properly (which is now done). This clearly duplicates some of what you've done here - though not the 'any' feature. However, we really like this idea and so have logged ticket ABU-673 in Jira for it as a likely future development item