Repository navigation
fix: normalize unavailable space homepages - #179
Merged
Merged
Conversation
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
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.
Confluence returned
homepageId: nullwhen creating a space during the release checks for #176. Both space response schemas rejected it, failing fixture setup before the content suite could run.Regenerate
SpaceandSpaceSummaryfrom apis-code-gen@d5ee7d6. Accept a null homepage ID and normalize it toundefinedthrough the existing compatibility helper, preserving the 3.2 optional string output type. Invalid non-string values still fail validation. Add 14 regression cases and an English patch changeset for the combined 3.3.0 release.Validation: generator typecheck and all 440 tests; SDK lint/typecheck, all 204 unit tests and build; assignability of 737 types and 348 method signatures against 3.2.0; all 20 targeted content/space live tests on Node 24. Full PR checks, including all live suites, are required before merge.