Skip to content

Fix runtime trait IDs - #817

Merged
jonathan343 merged 1 commit into
developfrom
fix/runtime-trait-ids
Sep 28, 2026
Merged

jonathan343 merged 1 commit into
developfrom
fix/runtime-trait-ids

Conversation

@jonathan343

@jonathan343 jonathan343 commented Sep 28, 2026 •

Copy link
Copy Markdown
Contributor

Summary

Correct the registered IDs for DefaultTrait, IdempotencyTokenTrait, and UnitTypeTrait to smithy.api#default, smithy.api#idempotencyToken, and smithy.api#unitType.

Generated schemas already use these IDs, but the runtime registrations contain a namespace typo and incorrect capitalization. This causes default traits to resolve as DynamicTrait and operation idempotency-token metadata to return None. The UNIT schema also stores its unit-type trait under an incorrect ID, so lookup by the canonical ID returns None.

Add three regression tests that fail on develop and a bugfix entry. No generator changes or token autofill behavior are included.


By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

@jonathan343
jonathan343 requested a review from a team as a code owner September 28, 2026 05:43
Correct the default, idempotency token, and unit type trait IDs so
schemas resolve typed traits and operation token metadata correctly.
Add three regression tests and a bugfix entry.
@jonathan343 jonathan343 changed the title Fix default and idempotency token trait IDs Fix runtime trait IDs Sep 28, 2026

@arandito arandito left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

:shipit:

@jonathan343
jonathan343 merged commit 89da5db into develop Sep 28, 2026
10 checks passed
@jonathan343
jonathan343 deleted the fix/runtime-trait-ids branch September 28, 2026 06:07
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants