Skip to content
New issue

Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.

#

By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? # to your account

Clarify when changing a List to a Set is considered breaking #12924

Open
wants to merge 1 commit into
base: main
Choose a base branch
from
Open

Clarify when changing a List to a Set is considered breaking #12924

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 3 additions & 1 deletion docs/content/breaking-changes/breaking-changes.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -57,7 +57,9 @@ For more information, see
* <a name="resource-schema-field-removal-or-rename"></a>Removing or renaming a field
* <a name="field-changing-type"></a> Changing field output type
* Between primitive types, like changing a String to an Integer
* Between complex types like changing a List to a Set.
* Between complex types like changing a List to a Set. Note that List -> Set
can be considered non-breaking if the field is unordered and the order
returned from the API changes unpredictably.
* Changing the field type between primitive and complex data
types is not possible. For this scenario, field renames are preferred.
* <a name="field-optional-to-required"></a> Making an optional field required or adding a new required field
Expand Down
Loading