Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Private Functions are not private #10

Open
RandomNoun7 opened this issue Apr 10, 2020 · 1 comment · May be fixed by #13
Open

Private Functions are not private #10

RandomNoun7 opened this issue Apr 10, 2020 · 1 comment · May be fixed by #13
Assignees
@joeypiccola

Comments

@RandomNoun7
Copy link
Contributor

Functions added to the Private folder of the module source code, after compilation into the PSM1 file are then all exported as public functions anway.

The build PSake tasks seems to need to be modified to ensure that there is an Export-ModuleMember command added that only exports the public function names.
@joeypiccola
Copy link
Owner

Yup... the psake tasks are a bit of a mess 👎 . Just started to look at those, hoping to revert to 💯 PowerShellBuild psake tasks. They just don't all work OOB, I'll dig in more.

@joeypiccola joeypiccola linked a pull request Apr 27, 2020 that will close this issue
Open
9 tasks
@joeypiccola joeypiccola self-assigned this Apr 27, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@joeypiccola joeypiccola

Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Use PowerShellBuild 0.4.0 for all psake tasks joeypiccola/PSPuppetOrchestrator
2 participants
@joeypiccola @RandomNoun7