That is, one that is not stored as part of the instance?
Or, should the current TaskSettings module be treated such, i.e., not being propagated to the instance?
An example is the "seating arrangements task". The long list of numbers is currently essentially duplicated in the instance: once in TaskSettings, once in Check. To avoid that duplication, the list would have to be moved from TaskSettings to TaskData (because TaskData is the only module not propagated to the instance). But then it would not be accessible from TaskSettings.validateSettings. Having another module, besides TaskData, which is dropped on instance generation would solve this issue.
That is, one that is not stored as part of the instance?
Or, should the current
TaskSettingsmodule be treated such, i.e., not being propagated to the instance?An example is the "seating arrangements task". The long list of numbers is currently essentially duplicated in the instance: once in
TaskSettings, once inCheck. To avoid that duplication, the list would have to be moved fromTaskSettingstoTaskData(becauseTaskDatais the only module not propagated to the instance). But then it would not be accessible fromTaskSettings.validateSettings. Having another module, besidesTaskData, which is dropped on instance generation would solve this issue.