Describe the bug
On the latest build of AOG-Taskcontroller we had a Boolean variable with a default value of 24 (instead of 0 / 1 ) and the Kverneland Tellus screen didn't like this.
Supporting Documentation
I wonder of this function should also check for the value being correct?
bool InputBoolean::get_is_valid(const std::map<std::uint16_t, std::shared_ptr> &objectPool) const
This won't really help because the IOP is uploaded as-is however we could perhaps create an iop-validator that would do an analysis and give a % value about the IOP completeness so if someone makes an IOP that has an out of range value it could be catched earlier.
I think such a validator might be a wise thing to add as a dedicated build step for projects containing iop files.
Describe the bug
On the latest build of AOG-Taskcontroller we had a Boolean variable with a default value of 24 (instead of 0 / 1 ) and the Kverneland Tellus screen didn't like this.
Supporting Documentation
I wonder of this function should also check for the value being correct?
bool InputBoolean::get_is_valid(const std::map<std::uint16_t, std::shared_ptr> &objectPool) const
This won't really help because the IOP is uploaded as-is however we could perhaps create an iop-validator that would do an analysis and give a % value about the IOP completeness so if someone makes an IOP that has an out of range value it could be catched earlier.
I think such a validator might be a wise thing to add as a dedicated build step for projects containing iop files.