Improve code reuse for Parameters in ParameterMap #2448
Labels
Extra Attention
Testers and Gate keepers should pay extra attention as this affects core aspects.
Framework
Issues and pull requests related to components in the Framework
Maintenance
Unassigned issues to be addressed in the next maintenance period.
Milestone
This issue was originally TRAC 1601
The ParameterMap currently stores Geometry::Parameter objects as its value type. On the surface it seems that the Parameter type offers very little over and above the more standard Property classes used by Algorithms.
We should look at whether the Geometry::Parameter classes can just be replaced and their functionality implemented with Property types as this would benefit on code sharing. We can then remove the separate, getIntParameter, getStringParameter etc methods on the component and simply have getParameter that returns an appropriate object, which can also be used in Python.
There is also a hole in the current mechanism whereby we can't do anything with the FitParameter class as it doesn't inherit from anything.
Keywords: Maintenance, Core
The text was updated successfully, but these errors were encountered: