Skip to content

module names should not be case sensitive #781

Closed
Closed
module names should not be case sensitive#781
Labels
Usability(LEGACY) Helps filter issues that might be higher priority because they directly affect usability

Description

@JamesWTruher
James Truher (JamesWTruher)
opened on Apr 7, 2016
PS> import-module pester
import-module : The specified module 'pester' was not loaded because no valid module file was found in any module
directory.
At line:1 char:1
+ import-module pester
+ ~~~~~~~~~~~~~~~~~~~~
    + CategoryInfo          : ResourceUnavailable: (pester:String) [Import-Module], FileNotFoundException
    + FullyQualifiedErrorId : Modules_ModuleNotFound,Microsoft.PowerShell.Commands.ImportModuleCommand

although import-module Pester worked just fine

Activity

  1. James Truher (JamesWTruher)
    added
    Issue-Questionideally support can be provided via other mechanisms, but sometimes folks do open an issue to get a
    Usability(LEGACY) Helps filter issues that might be higher priority because they directly affect usability
    on Apr 7, 2016

  2. vors commented on Apr 12, 2016

    @vors
    sergei (vors)
    on Apr 12, 2016
    Collaborator

    We express module names as a file-system-provider entity: filename.
    From that point of view, it reasonable to have them case-sensitive, since File-System-Provider is case-sensitive on linux.

    On the other hand, the UX is not good.

  3. Joey Aiello (joeyaiello)
    added
    ready
    and removed
    Issue-Questionideally support can be provided via other mechanisms, but sometimes folks do open an issue to get a
    on May 5, 2016

  4. joeyaiello commented on May 5, 2016

    @joeyaiello
    Joey Aiello (joeyaiello)
    on May 5, 2016
    Contributor

    Usability sync agrees:

    • First, we do a case-insensitive search. If it's unambiguous, we load the module.
    • If it's ambiguous, then we throw an error.

  5. andyleejordan commented on Jun 16, 2016

    @andyleejordan
    Andy Jordan (andyleejordan)
    on Jun 16, 2016
    Member

    Falls under #706.

  6. Andy Jordan (andyleejordan)
    closed this as completedon Jun 16, 2016
  7. Andy Jordan (andyleejordan)
    removed
    ready
    on Jun 16, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    Usability(LEGACY) Helps filter issues that might be higher priority because they directly affect usability

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions