Skip to content

Fully support module alias or symbolic version icase resolution #301

Description

@xdelaruelle

Icase implementation, introduced in Modules 4.4, should be refined to fully support module alias and symbolic version. Following cases are currently lacking support:

  • indirect alternative names, expressed in an icase manner, are not reported among alternative names
  • symbolic version targeting a modulefile in an icase manner, is not reported through avail results
  • when 1 alias matches exactly a module name and another alias matches also this module but in an icase manner, this second alias is not reported among alternative names

setModuleResolution procedure should be reworked to achieve a complete icase support on module aliases and symbolic versions.

No activity

Activity on this issue will appear here.

Activity

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

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions