Update entryPoints.js to use permissionClasses instead of permission property#191
Merged
Update entryPoints.js to use permissionClasses instead of permission property#191
Conversation
labkey-adam
approved these changes
Jul 9, 2024
labkey-adam
pushed a commit
that referenced
this pull request
Aug 1, 2024
…property (#191) - Update entryPoints.js to use permissionClasses instead of permission property - Remove entryPoints.js permission props for generateLib since they don't apply for libs
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 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.
Rationale
We are deprecating the
<permissions>properties for the view.xml files. This PR migrates those usages to<permissionClasses>.Changes