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.

Sign up for GitHub

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

Jump to bottom

Make compatible with composer v1 #1

Open
chillu opened this issue Jun 13, 2021 · 2 comments
Open

Make compatible with composer v1 #1

chillu opened this issue Jun 13, 2021 · 2 comments

Comments

@chillu
Copy link
Member

chillu commented Jun 13, 2021

If we don't do this, it effectively blocks anyone from using this plugin (and silverstripe/graphql:4) on Silverstripe's commercial platforms (CWP and Silverstripe Cloud). The upgrade to composer v2 for those platforms is planned, but ideally we don't create a two-way dependency there.
@maxime-rainville
Copy link

From memory, SCP/CWP block usage of plugins altogether. So making it composer-v1-compatible might not be enough.

@chillu
Copy link
Member Author

chillu commented Jun 14, 2021 •
edited
Loading

No, they run with --no-script, but without --no-plugins - I've confirmed this with TSP.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@chillu @maxime-rainville