Skip to content

Don't require very specific dependencies of upstream libraries #9

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

Merged
merged 1 commit into from
May 19, 2016

Conversation

deviantintegral
Copy link
Contributor

I'd like to be able to integrate Patternlab with another code base, but the to-the-patch-version dependencies in composer.json totally break that.

There's a question about the same issue on the commit at 6bb7c7b - I've yet to find any answer as to why this was done in the first place.

@bradfrost
Copy link
Member

Thanks for this @deviantintegral. I'm unfamiliar with this so I'll leave it to @dmolsen to explain the rationale and/or merge the pull request. Thanks!

@dmolsen
Copy link
Member

dmolsen commented Jan 23, 2016

At the time I did it it was because it was the only way to have Composer load dependencies in some semblance of rational order. I even opened an issue about this with Composer. I'll merge your changes with a test branch tomorrow and see if newer versions of Composer addressed it.

@dmolsen dmolsen merged commit 036fe70 into pattern-lab:master May 19, 2016
EvanLovely added a commit that referenced this pull request Oct 9, 2017
Replace possible dots in pattern names with dashes
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants