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

fix: Improve get caller file path util #7974

Merged
merged 5 commits into from
Jul 5, 2024
Merged

Conversation

adrien2p
Copy link
Member

@adrien2p adrien2p commented Jul 5, 2024

FIXES CORE-2492

Copy link

vercel bot commented Jul 5, 2024

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name Status Preview Comments Updated (UTC)
api-reference 🔄 Building (Inspect) Visit Preview 💬 Add feedback Jul 5, 2024 10:39am
medusa-dashboard ✅ Ready (Inspect) Visit Preview 💬 Add feedback Jul 5, 2024 10:39am
5 Skipped Deployments
Name Status Preview Comments Updated (UTC)
api-reference-v2 ⬜️ Ignored (Inspect) Visit Preview Jul 5, 2024 10:39am
docs-ui ⬜️ Ignored (Inspect) Visit Preview Jul 5, 2024 10:39am
docs-v2 ⬜️ Ignored (Inspect) Visit Preview Jul 5, 2024 10:39am
medusa-docs ⬜️ Ignored (Inspect) Visit Preview Jul 5, 2024 10:39am
resources-docs ⬜️ Ignored (Inspect) Visit Preview Jul 5, 2024 10:39am

Copy link

changeset-bot bot commented Jul 5, 2024

⚠️ No Changeset found

Latest commit: 5601a3a

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

Copy link
Contributor

@riqwan riqwan left a comment

Choose a reason for hiding this comment

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

🥇

@thetutlage
Copy link
Contributor

Just curious, where do we use this helper?

@adrien2p
Copy link
Member Author

adrien2p commented Jul 5, 2024

Just curious, where do we use this helper?

for the joiner config builder, basically since the choice was to make it fully magic and this builder is at different level in the application stack, I needed a way to retrieve the location of the original module caller

@adrien2p
Copy link
Member Author

adrien2p commented Jul 5, 2024

@thetutlage as I was explaining to carlos, since node deprecated the callee and that the require.resolve parent is deprecated as well, I didnt get a choice 😂 if you have anyhting in mind let me know

@thetutlage
Copy link
Contributor

@adrien2p Nope. I am not questioning the implementation. Just curious, where do we/in which use cases we look for the callee path?

@thetutlage
Copy link
Contributor

thetutlage commented Jul 5, 2024

for the joiner config builder, basically since the choice was to make it fully magic and this builder is at different level in the application stack, I needed a way to retrieve the location of the original module caller

Saw this comment now. Cool, makes sense!

@adrien2p adrien2p merged commit 1393f51 into develop Jul 5, 2024
23 checks passed
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