Earlier we were doing like - if it wasn't anything which would evaluate to False - which resulted in not able to turn 'off' any boolean field
I have a different fix for this one in a local branch where I fixed the SSE for custom fields.
So I'll likely close this one when I'll open the other if that's ok with you :)
Lol why won't it be okay with me?
On 13 Nov 2016 11:43 p.m., "Pierre-YvesChibon" pagure@pagure.io wrote:
pingou commented on the pull-request: Update key value in custom field when value is not None that you are following: `` I have a different fix for this one in a local branch where I fixed the SSE for custom fields. So I'll likely close this one when I'll open the other if that's ok with you :) `` To reply, visit the link below or just reply to this email https://pagure.io/pagure/pull-request/1547
pingou commented on the pull-request: Update key value in custom field when value is not None that you are following: `` I have a different fix for this one in a local branch where I fixed the SSE for custom fields.
Update key value in custom field when value is not None
So I'll likely close this one when I'll open the other if that's ok with you :) ``
To reply, visit the link below or just reply to this email https://pagure.io/pagure/pull-request/1547
Pull-Request has been closed by vivekanand1101
Because you worked on it? :)
Earlier we were doing like - if it wasn't anything which
would evaluate to False - which resulted in not able
to turn 'off' any boolean field