-
Notifications
You must be signed in to change notification settings - Fork 3
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
Write a guide for working with Composer #134
Labels
should have
Should be done, medium priority for now
Comments
Acquia have a good guide here https://support.acquia.com/hc/en-us/articles/360048081273-Using-Composer-to-manage-dependencies-in-Drupal-8-and-9 |
jennybeaumont
added
the
could have
Could be done, or nice to have, low priority for now
label
Sep 30, 2020
This is only a could have and is quite stale, closing. |
Reopening as there are some hard to debug composer issues and it would be useful to have a specific guide to point people to when they run into problems. |
roborourke
changed the title
Altis Dev Satisfaction Survey: Working with Composer
Write a guide for working with Composer
Feb 3, 2022
roborourke
added
should have
Should be done, medium priority for now
and removed
could have
Could be done, or nice to have, low priority for now
labels
Feb 3, 2022
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
From the survey, there is feedback from some developers who say they find it difficult to understand how does a Composer works. We could perhaps add more documentation to explain this.
Acceptance criteria:
The text was updated successfully, but these errors were encountered: