'RubricAssociation' object has no attribute 'id',

[zetaminer]

Describe the bug

Calling print() on a RubricAssociation object raises an AttributeError due to the str method attempting to access self.id, which does not exist on the object.

To Reproduce

1. Create a rubric and associate it with an assignment using canvasapi.
2. Attempt to print the returned RubricAssociation object directly using print(rubric_association).

rubric_association_info = {
      "rubric_association": {
          "rubric_id": rubric['rubric'].id,
          "association_id": assignment.id,
          "association_type": "Assignment",
          "title": assignment.name,
          "use_for_grading": True,
          "purpose": "grading",
          "bookmarked": True
          }
      }

rubric_association = course.create_rubric_association(**rubric_association_info)
print(rubric_association)

The following error is raised:
AttributeError: 'RubricAssociation' object has no attribute 'id'

Expected behavior

RubricAssociation.str() should not assume the object has an id attribute if it's not guaranteed to exist. It should fallback gracefully or be based on guaranteed attributes

Environment information

• Python version 3.12.8
• CanvasAPI version 3.3.0

Additional context

The Canvas API response for RubricAssociation includes an id field under the rubric_association key:

"rubric_association": {
  "id": 1617,
  ...
}

However, the canvasapi library does not merge this data into the top-level attributes of the RubricAssociation object. As a result, attributes like self.id are not accessible, and the following str method fails:
def str(self):
return "{}, {}".format(self.id, self.association_type)

Fix suggestions:

• Flatten the rubric_association dict into the root object data before initializing the RubricAssociation object.
• Or, modify str() to use getattr(self, "id", "N/A") as a failsafe.

[Thetwam]

@zetaminer Thanks for the bug report. It looks like the API endpoint returns a dict with two keys, each representing a different object: rubric and rubric_association. In canvasapi.course.Course.create_rubric(), we create canvasapi.rubric.Rubric and canvasapi.rubric.RubricAssociation objects from these, respectively.

At the moment, canvasapi.course.Course.create_rubric_association() just takes the raw data and turns it into a RubricAssociation object, which is definitely incorrect. The question is what's the best way to "fix" it? Each has ramifications on current implementations.

Options:

1. Follow the pattern from create_rubric(), and return a dictionary with keys rubric and rubric_association, containing a Rubric and RubricAssociation object, respectively.
2. Only grab the rubric_association part of the response and return RubricAssociation with it (throwing away the rest of the information)

#1 is more consistent with the other code, but #2 is a more in line with what's expected from the method name. To be honest, I could go either way. Either way, it's probably a breaking change. Let me know which you'd prefer, or if you have any questions/feedback.

[hanifjilani]

Hey @Thetwam . I would like to work on this and propose a solution. Let me know if your willing to assign it to me!

Thanks!

I will be working for a couple of weeks on these issues as part of my University Course on Open Source Contribution. I also currently working on the issue #702 , though I think that is going to be closed soon!