Add links and describe dev mod for extensions #750
Merged
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
|
🎊 PR Preview has been successfully built and deployed to https://localstack-docs-preview-pr-750.surge.sh 🎊 |
|
/cc @thrau I just saw in the eng. all-hands this might be partly related to R6 of the workstream "Improve Extensions UX". I pushed this out based on customer feedback missing the links and dev mode info. |
thrau
force-pushed
the
add-links-and-clarify-dev-usage-for-extensions
branch
from
9450fb2
to
9ea4b85
Compare
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.
Add links to GitHub repo and describe development mode for LocalStack Extensions (based on external feedback).
Content partly copied from the Extensions repo: https://github.com/localstack/localstack-extensions
Based on the latest updates from localstack/localstack-extensions#29
It might be a bit confusing to have two
LocalStack Extensionspages:At least, we should clarify the intent and cross-link accordingly. I guess the idea was to have the API and conceptual part covered under references and the actual extensions in the tools list 🤔 @HarshCasper