This repository was archived by the owner on Oct 7, 2026. It is now read-only.
Repository navigation
Improve error handling in workbench if AWS is not configured - #3
Merged
Merged
Conversation
tbroadley
reviewed
Mar 11, 2024
tbroadley
left a comment
Contributor
There was a problem hiding this comment.
Nice, thank you for catching this!
Would you mind rebasing this PR on main?
Contributor
Author
|
Sure, it's now rebased and casing was updated to match the most recent changes on main |
tbroadley
reviewed
Mar 12, 2024
tbroadley
approved these changes
Mar 12, 2024
This file contains hidden or 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
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
2 participants
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.
The readme states that AWS is optional, but
npm run destroycrashes without a proper AWS configuration.This fixes that