-
Notifications
You must be signed in to change notification settings - Fork 81
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
chore: aws-sdk-swift package structuring #803
Conversation
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.
Can we place all the code generated services within a folder Sources/Services/..
?
This way its much easier to find AWSClientRuntime
and its contents within xcode?
Additionally, we can do the same for the services in tests -> Tests/Services/..
Still working on it, I plan to put generated services in |
1331711
to
caadd01
Compare
caadd01
to
5add24b
Compare
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 looks great!
Nothing blocking, but a few minor questions/comments
Issue #
Fixes #776
Description of changes
Companion PR smithy-lang/smithy-swift#503
This PR foundation for testing story.
The repo now looks like
In future we will add Integration following the same structure.
I had trouble with getting the checks passed when any service test is enabled. swift cli fatal fails. I'm going to cut an issue to Swift team about it. However, devs can uncomment any test target and use it in Xcode without any problem.
Refrain to review Services dirs.
New/existing dependencies impact assessment, if applicable
Conventional Commits
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.