Get Activity not fully functional about todoist-ruby HOT 1 OPEN

@crimsonknave Thank you for pointing this out! Admittedly, I do not use the activity API much so it is not unsurprising that the implementation is too shallow/incomplete. Your contribution would be of great help.

Occasionally, I have surfaced OpenStructs, especially when returning values since that feels a bit more user-friendly and avoided typing the parameters when I can on input in large part because Todoist does have a tendency to make some rather breaking changes in its sync API.

Admittedly, it seems inelegant if we can't detect the type of object, and rely on magic strings. We could mitigate this by having constants defined, but the sheer number of magic constants is rather mind boggling so getting the codebase consistent would be a non-trivial exercise (plus the maintenance of it). What I ultimately chose to do instead is to throw caution and good coding practices to the wind and allow some flexibility in input parameters which has helped the library age rather gracefully. When new magic parameters come in, it does not force a large library rewrite but it more or less forces API users to not only understand how the library works, but unfortunately, also read the original document on Todoist.

Not sure if this answers any of your questions, but I'd love to see your PR and maybe we can go from there!

from todoist-ruby.