User story #5303
closed
User story #3014: Optionnal variables should not be nulled (if they are not system variables)
Use empty ("") value in place of null for variable that has the attribute maybeempty
Added by Nicolas CHARLES almost 10 years ago.
Updated about 9 years ago.
Category:
Web - Config management
Description
Don't write anymore null variable in place of empty variable if a variable is empty, and not a system variable
- Status changed from New to Pending technical review
- Assignee changed from Nicolas CHARLES to François ARMAND
- Status changed from Pending technical review to Pending release
- % Done changed from 0 to 100
Applied in changeset clerk:commit:8869dafa62ec6c732ae7a5066354b9f8803d24d3.
Applied in changeset clerk:commit:8c5961683a6db74902d12ee86ec81a095cb6f26e.
- Subject changed from Don't write null variable that has the attribute maybeempty is they are not system variable to Use empty ("") value in place of null for variable that has the attribute maybeempty
Today, when a variable that may be empty is actually empty, we set it's value to 'null'. This is against general working of scripting and cause unessecary test condition. So we will use the empty string '""' in place.
One exception: for internal, system variable, the meaning of null is special and is used to remove part of technique code, a little like a C preprocessor compiler and #IFDEF. So, for system variable, an empty value is kept to "null" until we evolve to a better way of dealing with that.
- Target version changed from 140 to 3.0.0~beta1
- Status changed from Pending release to Released
This bug has been fixed in Rudder 3.0.0~beta1 which was release on 01/12/2014.
- Category changed from 14 to Web - Config management
- Tracker changed from Enhancement to User story
Also available in: Atom
PDF
Updated by 
Updated by 
Updated by Matthieu CERDA 
Updated by 
Updated by