-
Notifications
You must be signed in to change notification settings - Fork 603
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
feat: start endpoint resolver generation #472
Conversation
Codecov Report
@@ Coverage Diff @@
## smithy-codegen #472 +/- ##
==================================================
+ Coverage 94.54% 95.17% +0.62%
==================================================
Files 68 72 +4
Lines 1284 1389 +105
Branches 256 272 +16
==================================================
+ Hits 1214 1322 +108
+ Misses 70 67 -3
Continue to review full report at Codecov.
|
AWS CodeBuild CI Report
Powered by github-codebuild-logs, available on the AWS Serverless Application Repository |
45d0cfa
to
bcf3d5b
Compare
AWS CodeBuild CI Report
Powered by github-codebuild-logs, available on the AWS Serverless Application Repository |
bcf3d5b
to
d2acbaa
Compare
AWS CodeBuild CI Report
Powered by github-codebuild-logs, available on the AWS Serverless Application Repository |
Now in each client you can run `yarn build` or `yarn pretest`. They are the same that build js files to `dist` folder. In the workspace root, you can run `yarn: build:all` to compile the whole workspace from .ts to .js. You can also `yarn: test:all` to run all the test we have. Furthermore, you can run `yarn test:functional` to run the hostname integration test. This script can only be called after the repo is compiled.
d2acbaa
to
fd42ffb
Compare
AWS CodeBuild CI Report
Powered by github-codebuild-logs, available on the AWS Serverless Application Repository |
fd42ffb
to
7e3eaf3
Compare
AWS CodeBuild CI Report
Powered by github-codebuild-logs, available on the AWS Serverless Application Repository |
AWS CodeBuild CI Report
Powered by github-codebuild-logs, available on the AWS Serverless Application Repository |
e581cfc
to
0daf9ad
Compare
AWS CodeBuild CI Report
Powered by github-codebuild-logs, available on the AWS Serverless Application Repository |
@mtdowling RIP is integrated in the client config, and functional test is added. But it only contain rds-data test case for now. We will add more cases as we generate more clients. This PR should be merged to unblock the client codegen. After we generate the clients then we can test whether all the clients can infer the hostname correctly |
AWS CodeBuild CI Report
Powered by github-codebuild-logs, available on the AWS Serverless Application Repository |
sha256 | ||
} = input; | ||
let signer: Provider<RequestSigner>; | ||
if (input.signer) signer = normalizeProvider(input.signer); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This should be expanded out into a block form. Short form if statements are generally harder to read, and this one in particular is hard to read because the else uses a block but the first if statement doesn't.
I also think some comments in here to say what's going on would be useful to help future maintainers follow the code
//do nothing | ||
} | ||
} | ||
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
nit: extra newlines
LanguageTarget target | ||
) { | ||
switch (target) { | ||
case BROWSER: |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
nit: You could omit the BROWSER and NODE entries in the switch.
AWS CodeBuild CI Report
Powered by github-codebuild-logs, available on the AWS Serverless Application Repository |
LGTM |
This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs and link to relevant comments in this thread. |
Issue #, if available:
Description of changes:
Adds support for endpoint generation.
The generated endpoints work in two modes:
partitionEndpoint
in the endpoints.json file to generate an endpoint. This is handled using recursion by referring the partitionEndpoint by name (goes back to using exact matching).Note: this implementation does not implement regex based guessing.
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.
Examples
data.iot
acm
rds-data
iam
budgets
sts