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
Not sure if this is a feature or a bug, but the FROST-Server (I'm using docker v2.3) erases all properties with empty strings as value. For example, I post the following Thing:
{
"name" : "Kitchen",
"description" : "The Kitchen in my house",
"properties" : {
"someProperty" : true,
"emptyProperty": ""
}
}
And when I do a query, the emptyProperty field is missing:
{
"name" : "Kitchen",
"description" : "The Kitchen in my house",
"properties" : {
"someProperty" : true
}
}
However, the emptyProperty is indeed in the database:
{
"someProperty": true,
"emptyProperty": ""
}
I check the standard and I couldn't find any mention to empty properties. Is this behavior intended?
The text was updated successfully, but these errors were encountered:
That behaviour is not explicitly specified. It's simply the default behaviour of (most) json libraries, to leave out empty strings.
That could probably be made into a configuration option.
Not sure if this is a feature or a bug, but the FROST-Server (I'm using docker v2.3) erases all properties with empty strings as value. For example, I post the following Thing:
And when I do a query, the
emptyProperty
field is missing:However, the
emptyProperty
is indeed in the database:I check the standard and I couldn't find any mention to empty properties. Is this behavior intended?
The text was updated successfully, but these errors were encountered: