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
Currently, a task is done via uploading a file. This ignores the cases where a file wouldn't make sense; for example, for a software engineering project linking a PR would make more sense. This is also the only way the user can upload a file except for report and presentation.
Therefore, I propose a different schema. Instead of file: File for a task, the field can be work: string. This string is a URL to the work. It can be an external link (e.g. to a PR on GitHub or a file already hosted somewhere). Alternatively, the user can also upload a file to our system and link the file in this field.1
Moreover, in a task's comments, a user can upload a file if it is needed. GitHub also does this to an extend, though its file types are limited.
Footnotes
While this may sound complicated, it can be done with a simple click on the user's side. Also, shame on GitHub if it can't render this as footnote properly. ↩
The text was updated successfully, but these errors were encountered:
Currently, a task is done via uploading a file. This ignores the cases where a file wouldn't make sense; for example, for a software engineering project linking a PR would make more sense. This is also the only way the user can upload a file except for report and presentation.
Therefore, I propose a different schema. Instead of
file: File
for a task, the field can bework: string
. This string is a URL to the work. It can be an external link (e.g. to a PR on GitHub or a file already hosted somewhere). Alternatively, the user can also upload a file to our system and link the file in this field.1Moreover, in a task's comments, a user can upload a file if it is needed. GitHub also does this to an extend, though its file types are limited.
Footnotes
While this may sound complicated, it can be done with a simple click on the user's side. Also, shame on GitHub if it can't render this as footnote properly. ↩
The text was updated successfully, but these errors were encountered: