Client doesn't send explicitely empty values #255

New issue

Closed

opened 2022-06-17 16:45:29 +02:00 by Jef Roosens · 2 comments

Jef Roosens commented

2022-06-17 16:45:29 +02:00

Owner

At least with the CLI this isn't possible, because the client code filters out empty values.

Jef Roosens added this to the 0.4.0 milestone 2022-06-17 16:45:29 +02:00

Jef Roosens added the

bug

label 2022-06-17 16:45:29 +02:00

Jef Roosens commented

2022-08-09 13:00:44 +02:00

Author

Owner

A way to fix this would be to properly process empty values for fields that can be empty, instead of treating each empty value the same as it being not provided at all.

Jef Roosens commented

2022-08-09 13:21:09 +02:00

Author

Owner

After some testing, it seems that the API is working properly. If branch= is passed as a parameter, the value is indeed set to the empty value again. The problem is the client code not sending empty values.

After some testing, it seems that the API is working properly. If `branch=` is passed as a parameter, the value is indeed set to the empty value again. The problem is the client code not sending empty values.

Jef Roosens changed title from ~~Once a Git branch value is set, it can't be removed~~ to Client doesn't send explicitely empty values

2022-08-09 13:21:26 +02:00

Jef Roosens self-assigned this 2022-09-04 22:55:58 +02:00

Jef Roosens referenced this issue from a pull request that will close it,

2022-09-11 22:27:24 +02:00

Some small fixes #273

Jef Roosens closed this issue

2022-10-01 16:56:26 +02:00

This repository is archived. You cannot comment on issues.