Preparations for PB Element Extension #4336
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
adrians5j
changed the title
Pavel910
approved these changes
Oct 17, 2024
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.
Changes
This PR just does a couple of preparations for the 5.41.1 release. Mainly, it creates the
Extensions.tsxfile in theapps/website/srcfolder, so that it can be used by the upcoming PB Element scaffold, which should come up with 5.41.1.Extra Changes
I also introduced the
@webiny/cli-plugin-extensionspackage, which, with the 5.41.1 release, will be the main package that deals with extensions-related scaffolding. It will also allow users to create extensions via thewebiny extensioncommand (instead ofwebiny scaffold extensions).How Has This Been Tested?
Manually.
Documentation
None for now.