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
Right now, the tool pulls all assignments from Canvas, and all tasks in Todoist. This results in a lot of overhead and impact (for example, I have 1800+ Todoist Tasks) and retrieving data that isn't needed.
It think architecturally it would be preferable if instead it iterated and submitted tasks on a per-course basis, pulling only the matching tasks for the project. This would significantly cut down on the amount of return, though it would require that we iterate through the process times for each class.
Thoughts on changing the logic flow? It would be more API calls, but significantly less data returned. I think it would help with performance and efficiency.
The text was updated successfully, but these errors were encountered:
Right now, the tool pulls all assignments from Canvas, and all tasks in Todoist. This results in a lot of overhead and impact (for example, I have 1800+ Todoist Tasks) and retrieving data that isn't needed.
It think architecturally it would be preferable if instead it iterated and submitted tasks on a per-course basis, pulling only the matching tasks for the project. This would significantly cut down on the amount of return, though it would require that we iterate through the process times for each class.
Thoughts on changing the logic flow? It would be more API calls, but significantly less data returned. I think it would help with performance and efficiency.
The text was updated successfully, but these errors were encountered: