[PSS 2014][Bug] Primal Sense and scoped functions

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 9 years and 4 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 2014][Bug] Primal Sense and scoped functions

Post by Bosparan »

PSS Version: 2014 4.1.74
OS Version: Windows 7 x64
WMF Version: 4.0

Impact: Frequent annoyance

Symptom:
Creating a scoped function (eg: 'script:Get-Test { ... }') will cause primal sense to treat the function as if the scope marker was part of the name.

Reproducibility:
Create script:
PowerShell Code
Double-click the code block to select all.
script:Get-Test
{
    ...
}
Then try receiving Primal Sense for it
- Typing "Get-Tes" will not provide PS
- Typing "script:get" will provide PS
This topic is 9 years and 4 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.