ui: oss don't ever POST/PUT Namespaces when writing data #7238
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
We missed a couple of places where we use the
nonEmptySet
function, whichwill only perform the set if the specified property is non-empty.
Currently we aren't certain there is a place in OSS where a
Namespace
can make its way down via the API and end up being PUT/POSTed back out
again when saved. If this did ever happen we would assume it would be
the default namespace, but additionally we add an extra check here to ensure we never
PUT/POST the Namespace property if Namespaces are disabled.
This additional check could be removed in the future.