Skip to content

fix: Support multiple internal extensions #74

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
Oct 8, 2024

Conversation

ServerlessLife
Copy link
Owner

No description provided.

@ServerlessLife ServerlessLife self-assigned this Oct 8, 2024
@ServerlessLife ServerlessLife force-pushed the fix-support-multiple-internal-extensions branch from 7d55aec to 11268ee Compare October 8, 2024 19:03
@ServerlessLife ServerlessLife merged commit 6227d90 into main Oct 8, 2024
10 checks passed
@ServerlessLife ServerlessLife deleted the fix-support-multiple-internal-extensions branch October 8, 2024 19:14
@ServerlessLife
Copy link
Owner Author

🎉 This issue has been resolved in version 1.2.1 🎉

The release is available on:

Your semantic-release bot 📦🚀

@markostru
Copy link
Contributor

LLD now works with two internal extensions as long as LLD is listed first. This should be fine since LLD sets this order by default. However, potential issues may still arise, so LLD displays a warning if it detects another internal extension.

Running additional extensions is only relevant in Observability mode. In normal mode, only the local code is executed. With this update, the configuration is preserved, allowing the original layer to be restored when LLD is removed."

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants