Keri Moyle
Keri Moyle
Some thoughts about `Issue` urls. - It's best practice to have human-friendly URLs -> we should use a string error code in the URL rather than the specification heading number....
Implementing the renumbering of the specifications document (as in https://github.com/cellml/cellml-specification/issues/24 ) means that we need to update the heading numbers given to errors/issues too.
Part of #799 needed me to create `ComponentEntity::componentIndex`, `Model::importSourceIndex` and `Model::unitsIndex` functions. This kind of functionality could be useful to other types too.
Throughout the code we should take advantage of having levels and specification categories for `Issues` so that they can be more useful to the user. Applies to the `Generator` class,...
This bug is coming from the differences in how we search for units in a model using the `findUnits` function (see below). I can understand searching for a name match...
Now that we have a `Unit` class, we should make better use of it: ie, making a units->unit(0) access etc. Also set/get methods for all the parameters stored. Currently the...
I'm not sure what's expected from this situation: where an imported component is parent to a concrete child? I didn't expect this though ... (edit: removed units to make the...
It would be really useful to be able to wipe broken models from the importer's library and/or clear it all out. Since the importer uses cached models before parsing new...
Since the `Issue` class changed to return just the `std::any` item from the `item()` function, instead of an `AnyItem` item, the behaviour of the bindings and the C++ version has...
We can segfault the importer by changing the url of a previously-resolved import source. In the short term, we should clear a model's imports before resolving again. In the longer...