Skip to content

Update to SerdeContext #11

New issue

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

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

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Oct 27, 2019
Merged

Update to SerdeContext #11

merged 1 commit into from
Oct 27, 2019

Conversation

kstich
Copy link
Contributor

@kstich kstich commented Oct 23, 2019

Updates the generator to use the SerdeContext instead of distinct utils.

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

@kstich kstich requested a review from srchase October 23, 2019 23:38
This commit updates Command and Protocol generation to match expected,
consolidated SerdeContext instead of distinct (de)serializers. It also
fixes issues in writing the serde dispatch.
@srchase srchase self-requested a review October 24, 2019 23:05
@kstich kstich merged commit 171b9c8 into develop Oct 27, 2019
@mtdowling mtdowling deleted the context_update branch October 28, 2019 19:02
AllanZhengYP added a commit that referenced this pull request Jan 14, 2022
* load different sdk defaults value from defaults mode

* resolveDefaultsModeConfig to accept a hash

* simplify node runtime config defaults mode resolution

* import defaults mode interfaces from smithy-client package
srchase pushed a commit to srchase/smithy-typescript that referenced this pull request Mar 17, 2023
…smithy-lang#495)

* load different sdk defaults value from defaults mode

* resolveDefaultsModeConfig to accept a hash

* simplify node runtime config defaults mode resolution

* import defaults mode interfaces from smithy-client package
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