feat: updates to several AIPs#1562
Merged
noahdietz merged 12 commits intoaip-dev:masterfrom Oct 23, 2025
Merged
Conversation
slevenick
approved these changes
Oct 9, 2025
jskeet
reviewed
Oct 10, 2025
jskeet
approved these changes
Oct 23, 2025
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
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.
Note: Each AIP update is broken out into its own commit for ease of review.
In AIP-180 we add guidance regarding string field value length changes, the potential user impact, and how to design this ahead of time. Internal bug post-team discussion. Additionally, we add guidance regarding changes to the format or construction of a field as part of the "semantic changes" guidance after a specific case hurt customers. Internal bug from producer feedback. Finally, we add an example of how adding components to an API, namely pagination, is not always compatible and can be tricky. Internal bug from producer feedback. Needs no linter update.
In AIP-126 we clarify that the allowed zero-value exception -
UNKNOWN- can be prefixed with the enum name to avoid collisions as is typical. Internal bug from producer/linter feedback. Linter already updated.In AIP-157 (and AIP-133/AIP-134) we explicitly allow and default value guidance for using the
Viewpattern in other standard methods, soft delete, and custom methods. Internal bug contains references of discussion and prior art. Needs linter update.In AIP-160, we clarify that the HAS operator can be used on top-level fields. Internal bug with references and tests.