Update article.md to expand on property order in objects#3368
Open
jvilders wants to merge 2 commits into
Open
Conversation
Expand explanation to make it more explicit that integer property names always come before any non-integer property names. Also add a small example to show this. Fix casing of object name Fix indexing Fix name Expand wording on object property order
Makes the integer property names more intuitive.
|
|
manohar-geekologix
approved these changes
Feb 16, 2023
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
3 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.
Current article does mention integer properties, but it's not explicit that these appear first in the object and the existing example doesn't feature this situation. I've made the wording more explicit and added a small, if somewhat contrived, example of this situation.