LPS-118832 Update private fields #384
Closed
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
…le book it should be the master page style book
… if the page is configured to inherit the stylebook. This is done when the stylebook entry id is 0
This new API will allow us to avoid adding dependencies to depot everywhere. We will now use these capability methods and add a custom depot implementation for depot groups. We can slowly add new methods when needed. For now we will use it to check for pages and portlet support for a given group.
…upported portlets
When users try to do something with the main structure of a file entry type, check permissions over the file entry type itself. This will avoid the need to assign permissions to both DLFileEntryType and DLFileEntryTypeMetadata.
…ommerce-elasticsearch7: Use future proof Index Settings Contributor (not tied to a specific Elasticsearch version) See: https://issues.liferay.com/browse/LPS-119024 https://issues.liferay.com/browse/LPS-121803 https://issues.liferay.com/browse/COMMERCE-4423 Co-authored-by: Adam Victor Nazareth Brandizzi <adam.brandizzi@liferay.com> Co-authored-by: André de Oliveira <andre.oliveira@liferay.com> Co-authored-by: Bryan Engler <bryan.engler@liferay.com> Co-authored-by: kevinccruz <kevin.cruz@liferay.com>
**:information_source: This is safe to backport to 7.3.x.** These are just maintenance updates to reflect the migration of the `liferay-amd-loader` project to the named scope (ie. `@liferay/amd-loader`) version of the package. There should be no behavioral changes, but this bring the project into a namespace that we fully control. There are some cascading side-effects of this, which mean that we have to additionally update `@liferay/npm-bundler-preset-liferay-dev` (because it references the loader), which in turn means we must update `@liferay/npm-scripts` (because it references the preset). Finally, we have to update `@liferay/npm-bundler` because it references the loader too. Release notes for all of these: - https://github.com/liferay/liferay-frontend-projects/releases/tag/amd-loader%2Fv4.3.1 - https://github.com/liferay/liferay-frontend-projects/releases/tag/npm-bundler-preset-liferay-dev%2Fv4.6.5 - https://github.com/liferay/liferay-frontend-projects/releases/tag/npm-scripts%2Fv33.1.4 - https://github.com/liferay/liferay-frontend-projects/releases/tag/npm-bundler%2Fv3.0.1
This reverts commit fbd81d6.
This reverts commit c6af102.
|
To conserve resources, the PR Tester does not automatically run for every pull. If your code changes were already tested in another pull, reference that pull in this pull so the test results can be analyzed. If your pull was never tested, comment "ci:test" to run the PR Tester for this pull. |
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.
No description provided.