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

Fully support module alias or symbolic version icase resolution #301

Open
xdelaruelle opened this issue Nov 19, 2019 · 0 comments
Open

Fully support module alias or symbolic version icase resolution #301

xdelaruelle opened this issue Nov 19, 2019 · 0 comments

Comments

@xdelaruelle
Copy link
Member

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant