Skip to content

Fully support PowerShell module (.psm1) files #2241

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
SetTrend opened this issue Oct 16, 2019 · 1 comment
Closed

Fully support PowerShell module (.psm1) files #2241

SetTrend opened this issue Oct 16, 2019 · 1 comment

Comments

@SetTrend
Copy link

It looks like the PowerShell extension doesn't fully support PowerShell module files (with .psm1 file extension).

Folding, for example, isn't supported.

It would be a great advantage if the PowerShell extension fully supported .psm1 files, too.

Well, in fact, it would be great to be able to debug these kind of files, too, without being required to always create a .ps1 stub file first (see #133). Suggestion: For debugging a PowerShell file, a dialog might pup up, enabling the user to edit the call to be made within the PowerShell module. The text entered could be used by the extension to create a stub .ps1 file in a temporary directory and run that file. This would keep the user from creating such file manually. The dialog should offer a history, so previous calls could easily be repeated.

@ghost ghost added the Needs: Triage Maintainer attention needed! label Oct 16, 2019
@SetTrend
Copy link
Author

Just noticed that code folding is in fact supported for PowerShell module files. It just took a lot of time for VS Code to finish Codelense.

So, I'm closing this proposal.

@SydneyhSmith SydneyhSmith removed the Needs: Triage Maintainer attention needed! label Oct 28, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants