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

Exposed directories don't work correctly for relative-path dependencies #20

Closed
scott1702 opened this issue Apr 5, 2018 · 2 comments · May be fixed by #43
Closed

Exposed directories don't work correctly for relative-path dependencies #20

scott1702 opened this issue Apr 5, 2018 · 2 comments · May be fixed by #43

Comments

@scott1702
Copy link

When composer dependencies are installed from relative paths, directories listed in the dependency's expose are not accessible in the expected public path

@maxime-rainville
Copy link
Contributor

That's probably got something to do with the symlinking of of folders. Did you try using the symlink option in your composer file?

{
    "repositories": [
        {
            "type": "path",
            "url": "../../packages/my-package",
            "options": {
                "symlink": false
            }
        }
    ]
}

Does using a custom behavior affect this issue?

@Zauberfisch
Copy link

Probably same bug as #34. I'd vote to close

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

Successfully merging a pull request may close this issue.

3 participants