You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on Aug 18, 2020. It is now read-only.
Just want to document this so I don't forget about it.
I'll try to do some more investigations on what happens tomorrow.
Description
When setting the new IntegerRequirement from PR #148 to a noninteger it fails and displays the message Unable to set the requirement., just as intended.
But if you then try to refresh the Requirements using Show Requirements the get request fails without an error message.
To fix it use Delete for the IntegerRequirement that you previously set to an illegal value.
Then Show Requirements works again.
The text was updated successfully, but these errors were encountered:
When setting a Parameter to an invalid value deserializing it will throw an exception, jusat as intended.
The problem is that the requirement content is set before deserialzing the value:
logger info s"Created requirement content for '$requirementId' and deserialized its content."
true
} catch {
casee: Exception=>
logger error s"Unable to instantiate requirement content. Exception: ${e.getMessage}"
false
}
So if deserializing the value throws an exception the requirement content will be set to a parameter witch cannot be deserialized cause the value is null.
Fixing this should be as simple es moving the call of deserialize() before setRequirementContent().
Just want to document this so I don't forget about it.
I'll try to do some more investigations on what happens tomorrow.
Description
When setting the new IntegerRequirement from PR #148 to a noninteger it fails and displays the message
Unable to set the requirement.
, just as intended.But if you then try to refresh the Requirements using
Show Requirements
the get request fails without an error message.To fix it use
Delete
for the IntegerRequirement that you previously set to an illegal value.Then
Show Requirements
works again.The text was updated successfully, but these errors were encountered: