Keri Moyle

Following discussion here: https://github.com/cellml/libcellml/pull/640#discussion_r500016124

At the moment we're checking (and rechecking ...) each individual units name. We only need to check the name once.

Importer should clear issues at the time of each resolveImports call.

6

At present we don't clear issues from the importer anywhere. I think we should do it for subsequent calls to `resolveImports`.

Would you expect adding a `Units` to an `ImportSource` which already belongs to a `Model` would also add the `Units` to the `Model`? ``` TEST(ImportSource, addToImportSourceAlsoAddsToModel) { auto m =...

Component::setMath() doesn't set the cellml namespace

3

There's a difference in behaviour between parsing a model's math and setting it through the API. This test prints two different MathML strings, and the "fixed" one doesn't have the...

We need to make it easier for users to instal libcellml by providing binaries on the website.

Default profile for generator differs?

10

The generator's profile changes depending on whether you call libcellml in Python or in C++... is this deliberate? I'd thought that the C profile was the default throughout? In Python:...

Importer: Giving an absolute path as URL should prevent adding baseFile

2

If we pass a baseFile into the importer when resolving a model which has imports specified with an absolute path, the baseFile still gets added to the path, and makes...

See discussion [here](https://github.com/cellml/cellml-specification/issues/335)

Distinguish between errorCount and issueCount

5

Since switching from the `Error` to the `Issue` class we have the ability to provide the user with messages that don't affect validity or operation of the program. In the...