fix: resolve Package type name collision with semantic aliases #62
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.
Summary
Resolves type name collision where two different Package types are both exported as "Package":
The code generator's collision handling exported the wrong one. This fix adds semantic aliases for clarity.
Changes
Package: Canonical alias for the full domain model (used in MediaBuy, updates, etc.)CreatedPackageReference: New alias for the minimal response type (used in CreateMediaBuySuccessResponse)stable.pyto import Package directly from package.py module to bypass collisionTest Results
All 18 type alias tests passing, including new Package-specific tests validating: