You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Per suggestion from @shauntruelove , the tasks.json file has a round_id field that can be a string.
In the scenario complex example repo, the tasks.json has multiple date as round_id.
The dates are used to identify each round in the filename, content of the files, etc. However, we also identify the name by round, for example, round 1 is the date "2020-01-01".
Should we either add a round_name field in the tasks.json file or should we have a specific place in the repo to store that information in a different format? or both?
The text was updated successfully, but these errors were encountered:
Per suggestion from @shauntruelove , the
tasks.json
file has around_id
field that can be a string.In the scenario complex example repo, the
tasks.json
has multiple date asround_id
.The dates are used to identify each round in the filename, content of the files, etc. However, we also identify the name by round, for example, round 1 is the date "2020-01-01".
Should we either add a round_name field in the
tasks.json
file or should we have a specific place in the repo to store that information in a different format? or both?The text was updated successfully, but these errors were encountered: