-
Notifications
You must be signed in to change notification settings - Fork 171
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
Update value of localPath for composable packages #1154
Conversation
Thanks @tworcester we're waiting on #1173 to resolve issues around 3rd-party PRs |
This is being weird, can you take a look at it again @tworcester? |
Sure thing, the test failures? |
@jeff-mccoy Please try again, I believe I fixed the issue. I ran the tests locally but not the |
Do we want to provide the ability to respect a full file path? If people already using zarf have worked around this issue prior to this change, this would break them similar to what we saw above. I think checking the provided |
Yeah I think that sounds reasonable and would prevent this from being a breaking change, even though it's also a bug fix. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Add sanity check for existing behavior (component path in import path) to support existing broken behavior. Should leave a warning to the user noting this is incorrect.
Changing to draft to make tracking easier. Please complete the requested changes and then change back to ready for review, thanks! |
Thank you! I likely won’t have time to get to this until next week. (Just wanted to drop a note so you know I haven’t dropped it) |
not a problem at all, we may pick up the rest this week if we can squeeze it in, thanks! |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Eventually ™️, I think it would be a good idea to not even bother with the os.Stat()
files from the parent directory perspective. Even though it's pretty unlikely, I think it's not that intuitive.
Of course since it's old behavior that we're trying not to break, it makes 110% sense to include in this PR for now!
Thank you for wrapping this up, apologies for being absent! |
## Description <!-- Please include a summary of the change. Any relevant motivation or context is also helpful, as well as any dependencies that are required for this change --> ## Related Issue <!--- This project prefers to accept pull requests related to open issues --> <!--- If suggesting a new feature or change, please discuss it in an issue first --> <!--- If fixing a bug, there should be an issue describing it with steps to reproduce --> Fixes #1153 ## Type of change - [x] Bug fix (non-breaking change which fixes an issue) --------- Co-authored-by: Megamind <[email protected]> Co-authored-by: Jonathan Perry <[email protected]>
Description
Related Issue
Fixes #1153
Type of change