In testcase.py in /advance in Line https://github.com/ibpsa/project1-boptest/blob/master/testcase.py#L279, the second check (and u[key]) was originally implemented to check for an input value of None. This is because Flask sends the value of inputs that are not specified by the user as None. This also works if the value is of type string, which the Flask API set up in api.py provides. However, if the value is of type float, as in the case of the BOPTEST-Service API and when using the json attribute of python requests from a client, and = 0, then this will cause the check to fail and the value will not be included in the overwriting.
dhblum
commented
1 year ago
In
testcase.pyin/advancein Line https://github.com/ibpsa/project1-boptest/blob/master/testcase.py#L279, the second check (and u[key]) was originally implemented to check for an input value ofNone. This is because Flask sends the value of inputs that are not specified by the user asNone. This also works if the value is of type string, which the Flask API set up inapi.pyprovides. However, if the value is of type float, as in the case of the BOPTEST-Service API and when using thejsonattribute of python requests from a client, and = 0, then this will cause the check to fail and the value will not be included in the overwriting.Related to https://github.com/ibpsa/project1-boptest/issues/528 and https://github.com/ibpsa/project1-boptest/issues/532.
FYI @kbenne