Repository navigation
Clarify 20-character limit for assignable permission set names - #251
Open
iti-maciej-filipowicz wants to merge 1 commit into
Open
iti-maciej-filipowicz wants to merge 1 commit into
iti-maciej-filipowicz wants to merge 1 commit into
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
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.
Fixes #166.
object-name-30-char-limit.mdlists permission sets under the general 30-character limit and recommends a 20–26-character descriptive name. For a permission set withAssignable = truethe limit is 20 characters (AL0305 remarks); 30 characters applies only toAssignable = false. An agent following the current article designs an assignable permission set name that fails to compile.Changes:
20-characters,permission-set,assignable,al0305.File name and slug unchanged.