feat: use portlet category "Client Extensions" by default, for new projects #1066
Conversation
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
Even though we are no longer using manifest.json for anything, technically, it still has some value as documentation of what the build did and how the artifact was configured. Thus, I'm maintaining it and adding the portlet category name to it too.
Member
Author
|
Released artifacts to npm for the three modified packages. |
Member
|
Iinm, this one does not require deps upgrade in DXP so we basically are done with this |
Member
Author
yes |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 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.
See https://issues.liferay.com/browse/LPS-172978.
The goal of this PR is to keep using
category.remote-appsfor old projects (that's detected becauseliferay.jsonis empty for them) but usecategory.client-extensionsfrom now on.