-
Notifications
You must be signed in to change notification settings - Fork 2
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
Import project data from Drupal.org #33
base: 8.x-3.x
Are you sure you want to change the base?
Conversation
edef901
to
a13bf4d
Compare
independently from the complicated issues that i already noticed in the d7 version I generally don't want that to be the reason holding back progress on this. we can figure that out at a later point, i'm pretty happy if we get a good foundation even if there are still legacy flaws. |
I'll respond to your other points later, but for now: The update XML file, don't worry about it being commited for now. It is in just for ease of development for now. I'm pretty sure there is a hardcoded path somewhere to /home/simplytest/www/... in there as well somewhere :p before any of this makes its way into HEAD, I'll remove those bits and make a squashed commit so that there is nothing in the git history. |
Can you tell I'm tired by how often I said 'for now' :P |
Might be related: https://www.drupal.org/node/2081551 |
Drupal.org restws is good, but it doesn't really have a lot of things that we need... Maybe we should file issues to have git tags/project releases and statistics added to the rest endpoint. It would also be good it we could make api requests based on the project short name rather than having to do a whole other lookup just to get node ID. I spoke to @andrewbelcher today and he pointed out to me that we can look up available tags/releases in composer as well so that might be another thing to co sider. |
This is to be able to have an autocomplete field for drupal project on the submission form.