there are few attributes which are introduced lately or already there but not present in components file needs to add to JSON.
_pauseWhenOffScreen_playsinline_preventForwardScrubbing_showVolumeControl_shouldResetAllAnswers_retry._routeToAssessment_shouldCollapseItems_items._graphic.attribution_classes & _setCompletionOn & comment (optional)_isRound_graphic.attribution_items._graphic.attribution_items._graphic.attributionthere can be more attributes which are new/unknown that we can add, suggest any if i missed.
these are present in example.json for each component and documented in the README - do we really need to add them to the default course's components.json as well?
Personally I think the .json files that come with the framework should just contain the settings necessary to create that particular course - plus any that are likely to be used the majority of the time (e.g. _attempts)
the correct place to list all possible settings and include comments should be example.json
we can skip some of them which are not necessary but attributes likes e.g _preventForwardScrubbing,_pauseWhenOffScreen,_shouldResetAllAnswers etc
i am not sure how of frequently designers see example.json and newly additions.
its better to add if we have!
I don't think designers in general necessarily look at components.json either. I really don't think that the right way to be educating people about new settings. We should be directing people to release notes/README/example.json - otherwise we're just wasting our time maintaining these.
Can we do both if it's useful?
Most helpful comment
I don't think designers in general necessarily look at components.json either. I really don't think that the right way to be educating people about new settings. We should be directing people to release notes/README/example.json - otherwise we're just wasting our time maintaining these.