Skip to content

Conversation

bbasata
Copy link
Contributor

@bbasata bbasata commented Jun 19, 2025

Description

ListResult.{Identity,Resource} can be "null" in a couple ways. This change handles both.

It also updates diagnostic messages to be more user-actionable.

Rollback Plan

  • If a change needs to be reverted, we will roll out an update to the code within 7 days.

Changes to Security Controls

None

@bbasata bbasata changed the title Listresource tidy ListResource: tidy diagnostic messages Jun 19, 2025
@bbasata bbasata force-pushed the listresource-tidy branch from 91cfa76 to 6075e3f Compare June 19, 2025 19:24
@bbasata bbasata force-pushed the listresource-tidy branch from 6075e3f to 7dce0b7 Compare June 19, 2025 19:38
@bbasata bbasata changed the title ListResource: tidy diagnostic messages ListResource: revisit handling of null ListResult fields Jun 19, 2025
@bbasata bbasata force-pushed the listresource-tidy branch from 62c8251 to 65651f6 Compare June 19, 2025 19:47
@bbasata bbasata marked this pull request as ready for review June 19, 2025 19:52
@bbasata bbasata requested a review from a team as a code owner June 19, 2025 19:52
@bbasata bbasata added this to the v1.16.0 milestone Jun 19, 2025
austinvalle
austinvalle previously approved these changes Jun 24, 2025
Copy link
Member

@austinvalle austinvalle left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM 👍🏻

Diagnostics: diag.Diagnostics{},
}
}

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Future consideration: Should we eventually add a NewListResultsWithDiag so that you always create results from the request struct? 🤔

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Maybe! If it's a diagnostics-only response, then we have ListResultsStreamDiagnostics() in this pull request. I did not put it on the request struct because (hand-waving) a diagnostics-only response does not deal in schema business.

Very open to 💡 to refine that API.

@bbasata bbasata requested a review from austinvalle June 25, 2025 12:39
Copy link
Member

@austinvalle austinvalle left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🚀

@bbasata bbasata merged commit 7d8104c into main Jun 25, 2025
35 checks passed
@bbasata bbasata deleted the listresource-tidy branch June 25, 2025 13:35
@github-actions github-actions bot locked as resolved and limited conversation to collaborators Jul 25, 2025
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants