Json file name prefix #35
Closed
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
Hi, |
nirsky
suggested changes
May 4, 2021
There was a problem hiding this comment.
Hey, thanks for your contribution!
This PR is partial and has a few issues.
jsonPrefixoption is better to be passed through the constructor options.- I suggest a more descriptive name for this option:
s3KeyPrefix - The option need to be added to all 3 parts: sns-producer, sqs-producer and sqs-consumer. If it won't be added to the consumer there will be no possible way to consume this message!
- Missing documentation
- Missing tests
|
Closing because of inactivity. If someone want to implement this feature, please open a new PR. New features and fixes are very welcome! 🙏 ❤️ |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
No description provided.