Introduce classes to represent concepts in update_releases.py

[obsidian-community]

Introduce classes to represent concepts in update_releases.py

[claremacrae]

Thanks to a pairing session today with @kometenstaub - and the merging of the resultant #313 - we now have fully formed Theme class, and also a new ThemeDownloadCount class.

In terms of options for what's next...

Possible improvements to the Theme-related code

• It's possible that ThemeDownloadCount could be adjusted to store the download data: at the moment, it just contains static methods.
• We could also move ThemeDownloadCount to its own separate file
• I'd like to replace the two calls to get_json_from_github(THEMES_JSON_FILE) with a get_community_themes() that takes care of creating the Theme objects...
  • Done: 2022-03-08
• Review uses of theme.get("field") and theme["field"] - and where possible, replace them with accessor methods.
  • Done: 2022-03-08
• Then remove Theme.get() and Theme.__getitem__()
  • Done: 2022-03-08

Possible bigger next steps

• Create a Plugin class
  • Done: 2022-03-10
• Create an Author class
  • We decided that it was not worth implementing. A link-checking function would be a better way of fixing #143.

[claremacrae]

Update from 2022-03-08: We've now finished work on themes.py. The data in Theme is fully encapsulated.

We plan next to implement a Plugin class.