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

[FEATURE] Add module_alias resolution capabilities - round 2 #8098

Closed
wants to merge 17 commits into from

Conversation

davidroeca
Copy link

@davidroeca davidroeca commented Sep 20, 2019

This PR picks up the work done by @bradennapier in #7185, rebasing his work to the master branch and adding a few changes for to support <PROJECT_ROOT>.

Still to do:

  • Additional tests requested by @samwgoldman here
  • Additional tests for module.system.node.resolve_dirname if this touches code related to that
  • Handle the relative paths from the initial PR I'm almost inclined to not tackle this one, since <PROJECT_ROOT> will be handled. Thoughts?
  • Final review from @nmote

Note that this is the first time I've gone through this codebase and also my first time writing OCaml. Please nitpick away! Not sure if I'm following all of the right style conventions.

@facebook-github-bot
Copy link
Contributor

Thank you for your pull request and welcome to our community. We require contributors to sign our Contributor License Agreement, and we don't seem to have you on file. In order for us to review and merge your code, please sign up at https://code.facebook.com/cla. If you are contributing on behalf of someone else (eg your employer), the individual CLA may not be sufficient and your employer may need the corporate CLA signed.

If you have received this in error or have any questions, please contact us at cla@fb.com. Thanks!

@facebook-github-bot
Copy link
Contributor

Thank you for signing our Contributor License Agreement. We can now accept your code for this (and any) Facebook open source project. Thanks!

~reader
loc
?resolution_acc
dir (spf "%s%s%s" dirname Filename.dir_sep r))) )
Copy link
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I can implement the same modified_dir logic here if it's also preferred to support <PROJECT_ROOT> for module.system.node.resolve_dirname

@goodmind goodmind requested a review from nmote September 21, 2019 04:57
@davidroeca davidroeca force-pushed the feature/resolve_aliases branch from 0171bd9 to 1069672 Compare September 24, 2019 03:17
@davidroeca
Copy link
Author

@nmote I added some of the incremental tests that were mentioned in the previous PR and think this is ready for review as long as we're ok with only supporting <PROJECT_ROOT>/alias and alias

@nmote nmote self-assigned this Oct 24, 2019
@davidroeca
Copy link
Author

@nmote anything?

@nmote
Copy link
Contributor

nmote commented Oct 28, 2019

Sorry for the delay. I think I'll be able to take a close look at this sometime this week.

@nmote
Copy link
Contributor

nmote commented Nov 1, 2019

I'll take a closer look shortly, but first I have a question. @gabelevi just added a config option called module.system.node.root_relative_dirname (d17ed03). See the release notes for v0.111 as well as #8156.

Does this intersect at all with what's been done here?

@nmote
Copy link
Contributor

nmote commented Nov 1, 2019

I've looked a little bit closer and @gabelevi's recent work does seem to be pretty similar to this. Could you let me know whether what he's done works for your goals? If not, could you explain what you need from this PR that his work doesn't accomplish, and I'll take another look?

Thanks for your patience on this.

@davidroeca
Copy link
Author

Looks to me like that PR should handle the main use cases I had in mind

@nmote
Copy link
Contributor

nmote commented Nov 4, 2019

If that's the case, should this be closed?

@davidroeca
Copy link
Author

Yes

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

Successfully merging this pull request may close these issues.

4 participants