Skip to content

This issue was moved to a discussion.

You can continue the conversation there. Go to discussion →

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

Poly sync not working properly for projects in sub-directories #184

Closed
olafurnielsen opened this issue Mar 11, 2024 · 1 comment
Closed

Comments

@olafurnielsen
Copy link

olafurnielsen commented Mar 11, 2024

Describe the bug

  • I'd like to be able to organize projects in sub-directories under the projects folder
  • poetry poly info correctly finds all projects, even those in nested directories
  • I can run poetry poly sync to have bricks added to pyproject.toml
  • But the generated path is always ../../bases

To Reproduce
Steps to reproduce the behavior:

  1. Create a project in a sub-directory under projects
  2. Run poetry poly sync
  3. Run poetry build-project within the respective project

Expected behavior
Relative paths to components/bases should be correct – f.x. ../../../bases for a project residing in projects/sub-directory/project_a

Desktop (please complete the following information):

  • OS: Mac OS 14.3.1
  • Python version: 3.12.2
  • Poetry version: 1.8.2
@DavidVujic
Copy link
Owner

Hi @olafurnielsen, thank you for submitting this issue!

The suggested structure is to have the projects folder at one level. The poly info command finds it because that is how the file lookup is currently developed, but that was not intended (more like by accident 😄).

I think you can structure this as you like (even if it is not recommended), but without using the poly sync command.

I will move this issue to the discussions 💡 section!

Repository owner locked and limited conversation to collaborators Mar 11, 2024
@DavidVujic DavidVujic converted this issue into discussion #185 Mar 11, 2024

This issue was moved to a discussion.

You can continue the conversation there. Go to discussion →

Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants