Added fix for adding annotations that are not strings in ontodoc

[francescalb]

Furthermore, reenabled test for ontodoc. This is still a minimal test, but I think it can be gradually expanded.

Lastly - because a new altLabel was added in the testontology, it was reveiled that the same entity is returned twice in get_by_label_all in test_prefix. Issue #511 was made bacause of this.

Description:

Type of change:

• Bug fix.
• New feature.
• Documentation update.

Checklist:

This checklist can be used as a help for the reviewer.

• Is the code easy to read and understand?
• Are comments for humans to read, not computers to disregard?
• Does a new feature has an accompanying new test (in the CI or unit testing schemes)?
• Has the documentation been updated as necessary?
• Does this close the issue?
• Is the change limited to the issue?
• Are errors handled for all outcomes?
• Does the new feature provide new restrictions on dependencies, and if so is this documented?

Comments:

[codecov-commenter]

Codecov Report

Merging #512 (9d29601) into master (6bba50d) will increase coverage by 2.38%.
The diff coverage is 100.00%.

@@            Coverage Diff             @@
##           master     #512      +/-   ##
==========================================
+ Coverage   63.08%   65.46%   +2.38%     
==========================================
  Files          16       16              
  Lines        3080     3081       +1     
==========================================
+ Hits         1943     2017      +74     
+ Misses       1137     1064      -73     

Impacted Files	Coverage Δ
ontopy/ontodoc.py	66.33% <100.00%> (+14.63%)	⬆️

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.

[CasperWA]

This could fail, I suppose, if the type of value cannot be cast to a str type.
You could instead wrap it in a try/except block, where you're catching TypeError and ValueError exceptions, re-raising them with an appropriate custom message?

[francescalb]

I discussed this with @jesper-friis , and we can't really see a situation in which this not enough. I think it is better to leave it as is, and update this if and when we find examples of situations in which a different handling is needed.

[CasperWA]

As you wish. Casting to str is in general quite generous in this case, so it's fine I suppose. However, I'd argue it's good convention to consider possible edge cases and try to catch them if possible so exception messages are clear and helpful.