Skip to content

Conversation

@manno
Copy link
Member

@manno manno commented Sep 25, 2024

I think they are not needed, yet they show up as empty in every resource 🤷

Null values for fields that either don't specify the nullable flag, or give it a false value, will be pruned before defaulting happens. If a default is present, it will be applied. When nullable is true, null values will be conserved and won't be defaulted.

// +nullable
    marks this field as allowing the "null" value.

// +optional
    specifies that this field is optional.

@manno manno requested a review from a team as a code owner September 25, 2024 15:57
@weyfonk weyfonk force-pushed the remove-empty-fields-from-gitrepo-bd branch 2 times, most recently from 4b2ac6f to f4046c6 Compare September 27, 2024 15:47
> Null values for fields that either don't specify the nullable flag, or give it a false value, will be pruned before defaulting happens. If a default is present, it will be applied. When nullable is true, null values will be conserved and won't be defaulted.

```
// +nullable
    marks this field as allowing the "null" value.

// +optional
    specifies that this field is optional.
```
@manno manno force-pushed the remove-empty-fields-from-gitrepo-bd branch from f4046c6 to dfee3d6 Compare October 8, 2024 09:36
@manno manno merged commit 0000841 into main Oct 9, 2024
12 checks passed
@manno manno deleted the remove-empty-fields-from-gitrepo-bd branch October 9, 2024 14:54
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants