[PSS 2016][Bug] Script Parameter spacing

This forum can be browsed by the general public. Posting is limited to current SAPIEN license holders with active maintenance and does not offer a response time guarantee.
Forum rules
DO NOT POST LICENSE NUMBERS, ACTIVATION KEYS OR ANY OTHER LICENSING INFORMATION IN THIS FORUM.
Only the original author and our tech personnel can reply to a topic that is created in this forum. If you find a topic that relates to an issue you are having, please create a new topic and reference the other in your post.

Any code longer than three lines should be added as code using the 'Select Code' dropdown menu or attached as a file.
This topic is 7 years and 10 months old and has exceeded the time allowed for comments. Please begin a new topic or use the search feature to find a similar but newer topic.
Bosparan
Posts: 290
Last visit: Fri Oct 08, 2021 11:59 am

[PSS 2016][Bug] Script Parameter spacing

Post by Bosparan »

PSS Version: 2016 5.2.122 x64
OS Version: Windows 10 x64
WMF Version: 5.0

Impact: Negligible

Symptom:
When manually editing the parameters for a script (but not for a function!), when manually inserting a parameter between two other parameters, upon creating the second new line the cursor jumps to the type-declaration of the next parameter.

Reproducibility:
Create a new PowerShell script-File and paste this to the top:
  1. Param (
  2.     [Switch]
  3.     $Foo,
  4.    
  5.     [string]
  6.     $Bar
  7. )
Then move the cursor to behind the comma and press "enter" twice.

Note:
As the impact-ranking says, it's not really any priority problem for me. Just thought I'd mention it since I have no idea how trivial or difficult to fix this might be.
User avatar
davidc
Posts: 5913
Last visit: Mon Jul 08, 2019 8:55 am
Been upvoted: 2 times

Re: [PSS 2016][Bug] Script Parameter spacing

Post by davidc »

This is a side affect of formatting it seems. We will take a look at it.

David
David
SAPIEN Technologies, Inc.
This topic is 7 years and 10 months old and has exceeded the time allowed for comments. Please begin a new topic or use the search feature to find a similar but newer topic.