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.

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

Refactoring: reporting functions & Compare-M365DSCConfigurations: should call Test-ModuleValidity and remove of Version should be improved. #2158

Closed
andikrueger opened this issue Jul 29, 2022 · 0 comments · Fixed by #2161
Assignees
Labels
Core Engine Enhancement New feature or request

Comments

@andikrueger
Copy link
Collaborator

Creating reports caused many errors over the past few weeks.

There were several improvements like #2142 and #1970
At the moment, each function implements a slightly different interpretation on how to remove the version from the configuration.
The latest addition of Test-ModuleValidity adds more complexity to maintain the code.

It would be great to create a function that is used bz all reporting functions. Keeping changes in sync would be more easier.

@andikrueger andikrueger added Enhancement New feature or request Core Engine labels Jul 29, 2022
@andikrueger andikrueger self-assigned this Jul 29, 2022
andikrueger added a commit to andikrueger/Microsoft365DSC that referenced this issue Jul 29, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Core Engine Enhancement New feature or request
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant