Skip to content

Conversation

@MrM40
Copy link

@MrM40 MrM40 commented Apr 20, 2025

Added how to get name or value by index-number.

PR Summary

PR Checklist

  • Descriptive Title: This PR's title is a synopsis of the changes it proposes.
  • Summary: This PR's summary describes the scope and intent of the change.
  • Contributor's Guide: I have read the contributors guide.
  • Style: This PR adheres to the style guide.

Added how to get name or value by index-number.
@github-actions
Copy link

Expectations

Thanks for your submission! Here's a quick note to provide you with some context for what to expect from the docs team and the process now that you've submitted a PR. Even if you've contributed to this repo before, we strongly suggest reading this information; it might have changed since you last read it.

To see our process for reviewing PRs, please read our editor's checklist and process for managing pull requests in particular. Below is a brief, high-level summary of what to expect, but our contributor guide has expanded details.

The docs team begins to review your PR if you request them to or if your PR meets these conditions:

  • It is not a draft PR.
  • It does not have a WIP prefix in the title.
  • It passes validation and build steps.
  • It does not have any merge conflicts.
  • You have checked every box in the PR Checklist, indicating you have completed all required steps and marked your PR as Ready to Merge.

You can always request a review at any stage in your authoring process, the docs team is here to help! You do not need to submit a fully polished and finished draft; the docs team can help you get content ready for merge.

While reviewing your PR, the docs team may make suggestions, write comments, and ask questions. When all requirements are satisfied, the docs team marks your PR as Approved and merges it. Once your PR is merged, it is included the next time the documentation is published. For this project, the documentation is published daily at 3 p.m. Pacific Standard Time (PST).

@learn-build-service-prod
Copy link
Contributor

Learn Build status updates of commit 49f87b7:

✅ Validation status: passed

File Status Preview URL Details
reference/docs-conceptual/learn/deep-dives/everything-about-pscustomobject.md ✅Succeeded View (>=powershell-5.1)

For more details, please refer to the build report.

For any questions, please:

Comment on lines +44 to +50
To get name or value by index-number

```powershell
$myObject.psobject.properties.Name[2]
$myObject.psobject.properts.Value[2]
```

Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This is not an appropriate example. You example returns the State property, not the Name property.

Copy link
Collaborator

@sdwheeler sdwheeler left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thank you for your submission. However, I don't think these changes add value to the article.

@sdwheeler sdwheeler closed this Apr 21, 2025
@sdwheeler sdwheeler added resolution-wont-fix Status - closed as won't fix do-not-merge Tag - closed without merging labels Apr 21, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

do-not-merge Tag - closed without merging resolution-wont-fix Status - closed as won't fix

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants