Skip to content

Install-Module pwshEmojiExplorer requires accepting -AllowClobber #5

@ahpooch

Description

@ahpooch

Hi @techthoughts2

I ran into a cmdlet name conflict issue when installing the pwshEmojiExplorer module, which requires accepting -AllowClobber for installation—something that's usually a bit off-putting when using modules. As it turns out, the problem is related to the Convert module being used. I created an issue in the Convert module project describing this problem.

From what I understand, the main reason for using the Convert module is the ConvertFrom-Clixml cmdlet. A cmdlet with the same name is not available in PowerShell 5.1 but is present in PowerShell 7. I was curious whether the behavior of ConvertFrom-Clixml from the Microsoft.PowerShell.Utility module matches that of the cmdlet from the Convert module. To test this, I forked the Convert module and renamed ConvertFrom-Clixml to ConvertFrom-Clixml2. As expected, in PowerShell 5.1, Get-AllEmoji throws an error in Import-XMLDataSet because it can't find the ConvertFrom-Clixml cmdlet, but the more interesting behavior is in PowerShell 7: Get-AllEmoji runs but returns only one emoji (Description: grinning face, Decimal: {128512}). Based on this, it seems the pwshEmojiExplorer module depends on ConvertFrom-Clixml from the Convert module.

What do you think about removing this dependency? I might not have conducted the analysis thoroughly enough, and there could be other dependencies on the Convert module, but if not, wouldn't you agree that incorporating the functionality of the ConvertFrom-Clixml cmdlet directly into the pwshEmojiExplorer module is a good solution? This would eliminate the dependency and the warnings about name conflicts during module installation.

Metadata

Metadata

Assignees

No one assigned

    Labels

    bugSomething isn't working

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions