Skip to content

feat: add client libraries #89

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 2 commits into from
Jun 14, 2019
Merged

feat: add client libraries #89

merged 2 commits into from
Jun 14, 2019

Conversation

seebees
Copy link
Contributor

@seebees seebees commented Jun 13, 2019

  • Adding client-node and client-browser
  • Update example-node modules to use client-node
  • Update integration-node modules to use client-node
  • Update integration-browser modules to use client-browser

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

@seebees seebees requested a review from a team June 13, 2019 21:50
seebees added 2 commits June 13, 2019 16:11
* Adding `client-node` and `client-browser`
* Update `example-node` modules to use`client-node`
* Update `integration-node ` modules to use `client-node`
* Update `integration-browser` modules to use `client-browser`
Copy link

@lizroth lizroth left a comment

Choose a reason for hiding this comment

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

Couple of questions, but I think we could go ahead and ship this unless these points concern you as well.


This module is for encryption and decryption in Node.js.
It is a composition of underlying modules.
It is intended to have every component of the AWS Encryption SDK.
Copy link

Choose a reason for hiding this comment

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

NP: Every? Would it be better to explain this in the context of the desired outcome? e.g. It is intended to have every component of the AWS Encryption SDK required to work with encrypting and decrypting messages in our message format using any key source we support?

@@ -13,5 +13,5 @@
* limitations under the License.
*/

export { decrypt, DecryptResult } from './decrypt'
export * from './decrypt'
Copy link

Choose a reason for hiding this comment

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

IANAJS developer: is this good practice or is being more explicit preferred?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

In this case no. The reason I changed this is that some types were not being exported and this was causing TypeScript to complain about portability.

I'm moving to have things that are 'private' in the module in their own file.

@seebees seebees merged commit 24c72da into aws:master Jun 14, 2019
@seebees seebees deleted the create-client-packages branch June 14, 2019 18:14
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