You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This is a often-updated issue that exists for discussing decisions regarding MediaElch's development.*
What is this issue?
This issue lists and describes planned features and other design decisions. It is intended for MediaElch's developers and may go into technical details. All of these issues are neither bug reports nor feature requests. They're not big enough to create new issues for them. But other developers may want to try and fix one of the issues below so I thought: Why not share my thoughts?
It's also easier to keep track of one issue with all development design decisions than to have multiple smaller issues.
Currently I could pass e.g. -400 as the thumb size. This should be validated. Furthermore if an element does not contain require sub-tags, the whole scanning process fails without notice. See #776, #846
Test Kodi XML
We now have Kodi XML tests 🎉 But for some reason QDomDocument.toString() is not deterministic... On each test run I get a different XML string. This is really annoying.
=> fixed in b671f29
Make EpisodeWriter testable
The EpisodeWriter is part of KodiXml which makes it difficult to test. Should be refactored just like MovieXmlWriter has been refactored.
Fixed in #775
Coverage
We already have a coverage target, so it should be easy to deploy the coverage information to e.g. codecov. This issue also implies that we should add more unit tests. This on the other hand requires a better separation of concerns of our code (see "Separation of UI and Business Logic").
fixed in #767
This is a often-updated issue that exists for discussing decisions regarding MediaElch's development.*
What is this issue?
This issue lists and describes planned features and other design decisions. It is intended for MediaElch's developers and may go into technical details. All of these issues are neither bug reports nor feature requests. They're not big enough to create new issues for them. But other developers may want to try and fix one of the issues below so I thought: Why not share my thoughts?
It's also easier to keep track of one issue with all development design decisions than to have multiple smaller issues.
Table of Contents
(order: importance from highest to lowest)
Validate advancedsettings.xmlTest Kodi XML(fixed in b671f29 )Make EpisodeWriter testableCoveragecppcheck warningsclang-tidy warningsshellcheck warningsAdd Homebrew packageUse the distribution's QuaZipValidate advancedsettings.xmlCurrently I could pass e.g. -400 as the thumb size. This should be validated.Furthermore if an element does not contain require sub-tags, the whole scanning process fails without notice.See #776, #846Test Kodi XMLWe now have Kodi XML tests🎉But for some reason QDomDocument.toString() is not deterministic...On each test run I get a different XML string. This is really annoying.=> fixed in b671f29
Make EpisodeWriter testableThe EpisodeWriter is part of KodiXml which makes it difficult to test. Should be refactored just like MovieXmlWriter has been refactored.Fixed in #775
CoverageWe already have acoverage
target, so it should be easy to deploy the coverage information to e.g. codecov. This issue also implies that we should add more unit tests. This on the other hand requires a better separation of concerns of our code (see "Separation of UI and Business Logic").fixed in #767
cppcheck warningsThere are many annoying cppcheck warnings. That's why we haven't enabled the cppcheck step on TravisCI. For a list of warnings, see: https://travis-ci.org/Komet/MediaElch/jobs/558031311clang-tidy warningsSame as cppcheck warnings but with clang-tidy.We now have a
.clang-tidy
shellcheck warningsshellcheck warns about bad-practices in shell scripts. Very useful but also very noisy.fixed in #770
Add Homebrew packagehttp://brew.sh
Already exists: https://formulae.brew.sh/cask/mediaelch
Use the distribution's QuaZip#756 but for CMakefixed in #758 and #765
The text was updated successfully, but these errors were encountered: