Type annotations and models

[crazyscientist]

• Added more type annotations
• Use E factory in models instead of extension code

[github-actions]

Coverage report

Click to see where and how coverage changed

File	Statements	Missing	Coverage	Coverage (new stmts)	Lines missing
osctiny
osc.py
osctiny/extensions
bs_requests.py
staging.py
osctiny/models
__init__.py
staging.py					55-61
osctiny/utils
base.py
changelog.py
Project Total

This report was generated by python-coverage-comment-action

[der-gabe]

Hey, while we're at it...

Would you mind adding a return type annotation of -> str to the __str__ and __unicode__ methods of the Entry class in osctiny/utils/changelog.py

I would have done so myself, but GitHub doesn't let me add comments and suggestions outside of the context of changes and I didn't just want to push my own commit into a branch I'm reviewing...

[crazyscientist]

Would you mind adding a return type annotation of -> str to the str and unicode methods of the Entry class in osctiny/utils/changelog.py

I was hoping you would not notice that oversight because __str__ and __unicode__ are kind of obvious, but it certainly would be most consequent. 👍 Done.

[der-gabe]

I have to admit that the use of ElementMaker is a bit tricky to understand, but I get it now and it does reduce some code duplication (if not total LOC, alas), so I'm fine with it.

LGTM!