-
Notifications
You must be signed in to change notification settings - Fork 172
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Endpoint for Submission Class that returns data from the "submission_comments" field ...? #581
Comments
As you mentioned, when you upload a comment in a submission with Now your script to avoid uploading duplicates really depends on your implementation of a
then you can first check if
To deal with the possibility that a comment might be edited manually on Canvas, you could check if the If for some reason you don't want to store the canvas_id in your database, I think you could simply add a boolean property |
I have a script that uploads comments to a specific assignment based on the course_id, user_id, etc. I know there is an
endpoint] (v1/courses/{course_id}/assignments/{assignment_id}/submissions/{user_id}) that returns information about the submission comments field. Is there a way to check to see if comments have been added to a particular assignment before, say, I upload comments in my script?
I don't think canvasapi has any function in the Submission class that would allow me to not produce duplicate comments uploaded to a student assignment. There is an "edit" function and also a "get_submission_peer_reviews" but I'm not sure the latter returns the data I would need.
Obviously, the script now doesn't have this check, so, as it stands currently, it'll just upload duplicate comments if I were to run the script more than once (say, by error).
My apologies ahead of time if there is a way to get this data and I just missed it. (Also, if this is a duplicate here in the issues arena, feel free to let me know that too!)
Thanks to everyone there that works on this repository—it's been a hugely significant for me and my workflows, that's for sure!
The text was updated successfully, but these errors were encountered: