Update sharepoint-naming-guidelines.md #980
Merged
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
Updated guidelines about internal names and their character limits
|
Learn Build status updates of commit cb4504e: ✅ Validation status: passed
For more details, please refer to the build report. For any questions, please:
|
|
Thanks for the update, @mkacena. Some of these things can be confusing! |
sympmarc
added
the
Sign off
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.
Category
Related issues
Contents of the Pull Request
Updated SharePoint naming guidelines about internal names of columns and their character limits. Previously, I updated the guidelines where I corrected the character limit which I thought was wrong - from 255 to 32. After further investigation, I found out that neither is completely correct, so I elaborated the section with description of various scenarios.