Clarify 20-character limit for assignable permission set names in object-name guidance
Nobody has claimed this yet.
Assessment
- Difficulty
- 1/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 91/100
- Issue type
- Documentation
- Clarity
- Clearly specified
- Activity status
- Active
- Domain
- documentation
Research direction
Start with microsoft/knowledge/style/object-name-30-char-limit.md and compare its permission-set guidance with the AL0305 remarks linked in the issue. Update the article to state the 20-character limit for Assignable = true, retain the 30-character rule for other permission sets, revise the best-practice range, and explain that exceeding the assignable limit is a compiler error.】【。
Written by the indexing model from the issue text.
Description
Affected guidance
microsoft/knowledge/style/object-name-30-char-limit.md
Problem
The article includes permission sets in its general 30-character object-name limit. Its Best Practice section also recommends a descriptive name in the 20-26-character range, with additional space reserved for an app prefix.
There is an exception for assignable permission sets. The AL0305 diagnostic remarks on Microsoft Learn state:
For permission sets specifically, the diagnostic will also be triggered, if a permission set with the
Assignableproperty set totrueexceeds 20 characters.
The documented limits for permission set names are therefore:
| Permission set configuration | Maximum name length |
|---|---|
Assignable = true |
20 characters |
Assignable = false |
30 characters |
Following the current guidance can produce an assignable permission set name of 21-30 characters that appears compliant with the article but triggers compiler diagnostic AL0305.
Suggested correction
- Qualify the general 30-character rule with the 20-character exception for permission sets where
Assignable = true. - Adjust the Best Practice section so the complete assignable permission set name, including any prefix or suffix, fits within 20 characters. The 20-26-character descriptive-name recommendation should not apply to these objects.
- Link to the AL0305 remarks and clarify that exceeding this limit is a compiler error, not only a publish-time validation concern.
The general 30-character guidance can remain, provided this exception is explicit.
- Dominant language
- AL
- Stars
- 213
- Forks
- 121
- Avg merge
- 3d 2h
- Merged PRs (30d)
- 33
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from microsoft/BCQuality
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
-
Invalid Assertion Open
Difficulty 4/5 3-5 days Newbie friendliness 45/100
-
documentation
Difficulty 3/5 1-2 days Newbie friendliness 75/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 55/100
-
Difficulty 5/5 Over a week Newbie friendliness 35/100
All issues in microsoft/BCQuality
Similar issues
-
user-reported
Difficulty 2/5 1-3 hours Newbie friendliness 85/100
Kong/developer.konghq.com#7316 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
HarperFast/skills#96 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
infinispan/infinispan#18150 ·
-
bug triage:deciding
Difficulty 1/5 Under an hour Newbie friendliness 88/100
open-telemetry/otel-arrow#4132 ·
-
Ecosystem: ClawMetry — the Qwen Code reader is now free and open source (follow-up to #9294 / #9338) Opencategory/integration priority/P3 scope/documentation status/ready-for-human type/feature-request
Difficulty 1/5 Under an hour Newbie friendliness 84/100