📝 docs: improve example formatting in PhoneNumber documentation #347
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
hengky-kurniawan-1
force-pushed
the
fix-indent
branch
from
ae23fbd to
4b13bd8
Compare
yezz123
approved these changes
Oct 20, 2025
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.
This PR fixes formatting issues in the PhoneNumber documentation examples by correcting indentation and replacing incorrect comment markers (
>> ...with# > ...).These issues previously caused code examples to fail when copied directly from the docs.
With this update, the examples are now consistent, clear, and executable as intended, improving the overall reliability and usability of the documentation.