René's URL Explorer Experiment


Title: Indentation for lines after a pipe character · Issue #184 · PoshCode/PowerShellPracticeAndStyle · GitHub

Open Graph Title: Indentation for lines after a pipe character · Issue #184 · PoshCode/PowerShellPracticeAndStyle

X Title: Indentation for lines after a pipe character · Issue #184 · PoshCode/PowerShellPracticeAndStyle

Description: When we have multiple commands, each piping their output to one another, for readability / single-line width it's generally best to put each command on a different line; like so: Write-Verbose 'Before the stuff in the piped code' $myArra...

Open Graph Description: When we have multiple commands, each piping their output to one another, for readability / single-line width it's generally best to put each command on a different line; like so: Write-Verbose 'Bef...

X Description: When we have multiple commands, each piping their output to one another, for readability / single-line width it's generally best to put each command on a different line; like so: Write-Verbose ...

Opengraph URL: https://github.com/PoshCode/PowerShellPracticeAndStyle/issues/184

X: @github

direct link

Domain: patch-diff.githubusercontent.com


Hey, it has json ld scripts:
{"@context":"https://schema.org","@type":"DiscussionForumPosting","headline":"Indentation for lines after a pipe character","articleBody":"When we have multiple commands, each piping their output to one another, for readability / single-line width it's generally best to put each command on a different line; like so:\r\n\r\n```powershell\r\nWrite-Verbose 'Before the stuff in the piped code'\r\n$myArrayOfThings |\r\n    Where-Object {$_.SomeText -like 'pattern*'} |\r\n    ForEach-Object {[PSCustomObject]@{\r\n        MyText = $_.SomeText -replace '^pattern', ''\r\n        AnotherProperty = $_.SomethingElse\r\n    }}\r\nWrite-Verbose 'No longer in the piped code'\r\n```\r\n\r\nShould we define a best practice / guideline for this scenario?\r\n\r\nGenerally I indent all lines after the initial pipe to show they're a continuation of the  previous line.  However I don't indent again after subsequent lines because there would be no additional benefit.\r\n\r\nThe downside with this approach is that there's no \"closing line\"; which looks nasty if you the following line is a close for a parent block; e.g. \r\n\r\n```powershell\r\nif ($someFlag) {\r\n    $myArrayOfThings |\r\n        Where-Object {$_.SomeText -like 'pattern*'} |\r\n        ForEach-Object {[PSCustomObject]@{\r\n            MyText = $_.SomeText -replace '^pattern', ''\r\n            AnotherProperty = $_.SomethingElse\r\n        }}\r\n} # here we 're now have 8 spaces between this line's indentation level and the preceding line's.\r\n```\r\n\r\nAn option to tidy this up could be to put a comment to represent the close of he piped \"block\" / maybe with something after the comment character to show it's a close for the piped input; e.g.\r\n\r\n```powershell\r\nif ($someFlag) {\r\n    $myArrayOfThings |\r\n        Where-Object {$_.SomeText -like 'pattern*'} |\r\n        ForEach-Object {[PSCustomObject]@{\r\n            MyText = $_.SomeText -replace '^pattern', ''\r\n            AnotherProperty = $_.SomethingElse\r\n        }}\r\n    # |\r\n}\r\n```\r\n\r\nAnother option could be to put parentheses around the block.\r\n\r\n\r\n```powershell\r\nif ($someFlag) {\r\n    ($myArrayOfThings |\r\n        Where-Object {$_.SomeText -like 'pattern*'} |\r\n        ForEach-Object {[PSCustomObject]@{\r\n            MyText = $_.SomeText -replace '^pattern', ''\r\n            AnotherProperty = $_.SomethingElse\r\n        }}\r\n    )\r\n}\r\n```\r\n\r\n\r\nDo others have any thoughts or preferences on how best to approach these scenarios?","author":{"url":"https://github.com/JohnLBevan","@type":"Person","name":"JohnLBevan"},"datePublished":"2023-10-23T14:12:48.000Z","interactionStatistic":{"@type":"InteractionCounter","interactionType":"https://schema.org/CommentAction","userInteractionCount":3},"url":"https://github.com/184/PowerShellPracticeAndStyle/issues/184"}

route-pattern/_view_fragments/issues/show/:user_id/:repository/:id/issue_layout(.:format)
route-controllervoltron_issues_fragments
route-actionissue_layout
fetch-noncev2:d68783d9-8985-ba63-479b-3fedfa9e9725
current-catalog-service-hash81bb79d38c15960b92d99bca9288a9108c7a47b18f2423d0f6438c5b7bcd2114
request-idDB9A:DF89D:6B7F4F:93F554:69775581
html-safe-nonceaea6f6dab690612a3085fcbed26ee8fe22103d2420bc7431f7a2f35fc652155e
visitor-payloadeyJyZWZlcnJlciI6IiIsInJlcXVlc3RfaWQiOiJEQjlBOkRGODlEOjZCN0Y0Rjo5M0Y1NTQ6Njk3NzU1ODEiLCJ2aXNpdG9yX2lkIjoiMTAwNjY2NDY2NzIxODAwNzQyNSIsInJlZ2lvbl9lZGdlIjoiaWFkIiwicmVnaW9uX3JlbmRlciI6ImlhZCJ9
visitor-hmace3a43e6c82300b56928f6139948c4bb0b3ab5c56f5caead6485ad811f295606d
hovercard-subject-tagissue:1957275516
github-keyboard-shortcutsrepository,issues,copilot
google-site-verificationApib7-x98H0j5cPqHWwSMm6dNU4GmODRoqxLiDzdx9I
octolytics-urlhttps://collector.github.com/github/collect
analytics-location///voltron/issues_fragments/issue_layout
fb:app_id1401488693436528
apple-itunes-appapp-id=1477376905, app-argument=https://github.com/_view_fragments/issues/show/PoshCode/PowerShellPracticeAndStyle/184/issue_layout
twitter:imagehttps://opengraph.githubassets.com/e03213eb6fd044fd4c4c4be7837c94afe9fac0aa0fb56a57770c994298b097b6/PoshCode/PowerShellPracticeAndStyle/issues/184
twitter:cardsummary_large_image
og:imagehttps://opengraph.githubassets.com/e03213eb6fd044fd4c4c4be7837c94afe9fac0aa0fb56a57770c994298b097b6/PoshCode/PowerShellPracticeAndStyle/issues/184
og:image:altWhen we have multiple commands, each piping their output to one another, for readability / single-line width it's generally best to put each command on a different line; like so: Write-Verbose 'Bef...
og:image:width1200
og:image:height600
og:site_nameGitHub
og:typeobject
og:author:usernameJohnLBevan
hostnamegithub.com
expected-hostnamegithub.com
None3310064f35a62c06a4024ba37f41c06836f39376a095c2dfd2c4b693c34965be
turbo-cache-controlno-preview
go-importgithub.com/PoshCode/PowerShellPracticeAndStyle git https://github.com/PoshCode/PowerShellPracticeAndStyle.git
octolytics-dimension-user_id5641451
octolytics-dimension-user_loginPoshCode
octolytics-dimension-repository_id17317123
octolytics-dimension-repository_nwoPoshCode/PowerShellPracticeAndStyle
octolytics-dimension-repository_publictrue
octolytics-dimension-repository_is_forkfalse
octolytics-dimension-repository_network_root_id17317123
octolytics-dimension-repository_network_root_nwoPoshCode/PowerShellPracticeAndStyle
turbo-body-classeslogged-out env-production page-responsive
disable-turbofalse
browser-stats-urlhttps://api.github.com/_private/browser/stats
browser-errors-urlhttps://api.github.com/_private/browser/errors
release67d5f8d1d53c3cc4f49fc3bb8029933c3dc219e6
ui-targetfull
theme-color#1e2327
color-schemelight dark

Links:

Skip to contenthttps://patch-diff.githubusercontent.com/PoshCode/PowerShellPracticeAndStyle/issues/184#start-of-content
https://patch-diff.githubusercontent.com/
Sign in https://patch-diff.githubusercontent.com/login?return_to=https%3A%2F%2Fgithub.com%2FPoshCode%2FPowerShellPracticeAndStyle%2Fissues%2F184
GitHub CopilotWrite better code with AIhttps://github.com/features/copilot
GitHub SparkBuild and deploy intelligent appshttps://github.com/features/spark
GitHub ModelsManage and compare promptshttps://github.com/features/models
MCP RegistryNewIntegrate external toolshttps://github.com/mcp
ActionsAutomate any workflowhttps://github.com/features/actions
CodespacesInstant dev environmentshttps://github.com/features/codespaces
IssuesPlan and track workhttps://github.com/features/issues
Code ReviewManage code changeshttps://github.com/features/code-review
GitHub Advanced SecurityFind and fix vulnerabilitieshttps://github.com/security/advanced-security
Code securitySecure your code as you buildhttps://github.com/security/advanced-security/code-security
Secret protectionStop leaks before they starthttps://github.com/security/advanced-security/secret-protection
Why GitHubhttps://github.com/why-github
Documentationhttps://docs.github.com
Bloghttps://github.blog
Changeloghttps://github.blog/changelog
Marketplacehttps://github.com/marketplace
View all featureshttps://github.com/features
Enterpriseshttps://github.com/enterprise
Small and medium teamshttps://github.com/team
Startupshttps://github.com/enterprise/startups
Nonprofitshttps://github.com/solutions/industry/nonprofits
App Modernizationhttps://github.com/solutions/use-case/app-modernization
DevSecOpshttps://github.com/solutions/use-case/devsecops
DevOpshttps://github.com/solutions/use-case/devops
CI/CDhttps://github.com/solutions/use-case/ci-cd
View all use caseshttps://github.com/solutions/use-case
Healthcarehttps://github.com/solutions/industry/healthcare
Financial serviceshttps://github.com/solutions/industry/financial-services
Manufacturinghttps://github.com/solutions/industry/manufacturing
Governmenthttps://github.com/solutions/industry/government
View all industrieshttps://github.com/solutions/industry
View all solutionshttps://github.com/solutions
AIhttps://github.com/resources/articles?topic=ai
Software Developmenthttps://github.com/resources/articles?topic=software-development
DevOpshttps://github.com/resources/articles?topic=devops
Securityhttps://github.com/resources/articles?topic=security
View all topicshttps://github.com/resources/articles
Customer storieshttps://github.com/customer-stories
Events & webinarshttps://github.com/resources/events
Ebooks & reportshttps://github.com/resources/whitepapers
Business insightshttps://github.com/solutions/executive-insights
GitHub Skillshttps://skills.github.com
Documentationhttps://docs.github.com
Customer supporthttps://support.github.com
Community forumhttps://github.com/orgs/community/discussions
Trust centerhttps://github.com/trust-center
Partnershttps://github.com/partners
GitHub SponsorsFund open source developershttps://github.com/sponsors
Security Labhttps://securitylab.github.com
Maintainer Communityhttps://maintainers.github.com
Acceleratorhttps://github.com/accelerator
Archive Programhttps://archiveprogram.github.com
Topicshttps://github.com/topics
Trendinghttps://github.com/trending
Collectionshttps://github.com/collections
Enterprise platformAI-powered developer platformhttps://github.com/enterprise
GitHub Advanced SecurityEnterprise-grade security featureshttps://github.com/security/advanced-security
Copilot for BusinessEnterprise-grade AI featureshttps://github.com/features/copilot/copilot-business
Premium SupportEnterprise-grade 24/7 supporthttps://github.com/premium-support
Pricinghttps://github.com/pricing
Search syntax tipshttps://docs.github.com/search-github/github-code-search/understanding-github-code-search-syntax
documentationhttps://docs.github.com/search-github/github-code-search/understanding-github-code-search-syntax
Sign in https://patch-diff.githubusercontent.com/login?return_to=https%3A%2F%2Fgithub.com%2FPoshCode%2FPowerShellPracticeAndStyle%2Fissues%2F184
Sign up https://patch-diff.githubusercontent.com/signup?ref_cta=Sign+up&ref_loc=header+logged+out&ref_page=%2F%3Cuser-name%3E%2F%3Crepo-name%3E%2Fvoltron%2Fissues_fragments%2Fissue_layout&source=header-repo&source_repo=PoshCode%2FPowerShellPracticeAndStyle
Reloadhttps://patch-diff.githubusercontent.com/PoshCode/PowerShellPracticeAndStyle/issues/184
Reloadhttps://patch-diff.githubusercontent.com/PoshCode/PowerShellPracticeAndStyle/issues/184
Reloadhttps://patch-diff.githubusercontent.com/PoshCode/PowerShellPracticeAndStyle/issues/184
PoshCode https://patch-diff.githubusercontent.com/PoshCode
PowerShellPracticeAndStylehttps://patch-diff.githubusercontent.com/PoshCode/PowerShellPracticeAndStyle
Notifications https://patch-diff.githubusercontent.com/login?return_to=%2FPoshCode%2FPowerShellPracticeAndStyle
Fork 294 https://patch-diff.githubusercontent.com/login?return_to=%2FPoshCode%2FPowerShellPracticeAndStyle
Star 2.4k https://patch-diff.githubusercontent.com/login?return_to=%2FPoshCode%2FPowerShellPracticeAndStyle
Code https://patch-diff.githubusercontent.com/PoshCode/PowerShellPracticeAndStyle
Issues 37 https://patch-diff.githubusercontent.com/PoshCode/PowerShellPracticeAndStyle/issues
Pull requests 1 https://patch-diff.githubusercontent.com/PoshCode/PowerShellPracticeAndStyle/pulls
Discussions https://patch-diff.githubusercontent.com/PoshCode/PowerShellPracticeAndStyle/discussions
Actions https://patch-diff.githubusercontent.com/PoshCode/PowerShellPracticeAndStyle/actions
Projects 0 https://patch-diff.githubusercontent.com/PoshCode/PowerShellPracticeAndStyle/projects
Wiki https://patch-diff.githubusercontent.com/PoshCode/PowerShellPracticeAndStyle/wiki
Security 0 https://patch-diff.githubusercontent.com/PoshCode/PowerShellPracticeAndStyle/security
Insights https://patch-diff.githubusercontent.com/PoshCode/PowerShellPracticeAndStyle/pulse
Code https://patch-diff.githubusercontent.com/PoshCode/PowerShellPracticeAndStyle
Issues https://patch-diff.githubusercontent.com/PoshCode/PowerShellPracticeAndStyle/issues
Pull requests https://patch-diff.githubusercontent.com/PoshCode/PowerShellPracticeAndStyle/pulls
Discussions https://patch-diff.githubusercontent.com/PoshCode/PowerShellPracticeAndStyle/discussions
Actions https://patch-diff.githubusercontent.com/PoshCode/PowerShellPracticeAndStyle/actions
Projects https://patch-diff.githubusercontent.com/PoshCode/PowerShellPracticeAndStyle/projects
Wiki https://patch-diff.githubusercontent.com/PoshCode/PowerShellPracticeAndStyle/wiki
Security https://patch-diff.githubusercontent.com/PoshCode/PowerShellPracticeAndStyle/security
Insights https://patch-diff.githubusercontent.com/PoshCode/PowerShellPracticeAndStyle/pulse
New issuehttps://patch-diff.githubusercontent.com/login?return_to=https://github.com/PoshCode/PowerShellPracticeAndStyle/issues/184
New issuehttps://patch-diff.githubusercontent.com/login?return_to=https://github.com/PoshCode/PowerShellPracticeAndStyle/issues/184
Indentation for lines after a pipe characterhttps://patch-diff.githubusercontent.com/PoshCode/PowerShellPracticeAndStyle/issues/184#top
https://github.com/JohnLBevan
https://github.com/JohnLBevan
JohnLBevanhttps://github.com/JohnLBevan
on Oct 23, 2023https://github.com/PoshCode/PowerShellPracticeAndStyle/issues/184#issue-1957275516
https://github.com
Termshttps://docs.github.com/site-policy/github-terms/github-terms-of-service
Privacyhttps://docs.github.com/site-policy/privacy-policies/github-privacy-statement
Securityhttps://github.com/security
Statushttps://www.githubstatus.com/
Communityhttps://github.community/
Docshttps://docs.github.com/
Contacthttps://support.github.com?tags=dotcom-footer

Viewport: width=device-width


URLs of crawlers that visited me.