Timeline for drupal/core vs. drupal/core-recommended
Current License: CC BY-SA 4.0
5 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Aug 22, 2021 at 17:27 | comment | added | leymannx | @awm – No only one. | |
| Aug 18, 2021 at 18:24 | comment | added | awm | coming to this now, does this ( the second quoted paragraph) mean it ok to have both core-recommeded and drupal/core required in composer.json? | |
| Jul 5, 2021 at 20:50 | comment | added | sea26.2 | @leymannx Actually, the README referenced above explains very little. In drupalize.me/tutorial/…, there is the following: drupalize.me/tutorial/…" But, that still leaves a bucket of muddy water. Is best practice to pin versions or not? Does it appy to core or contrib or both? | |
| Jul 29, 2020 at 8:02 | comment | added | adrum99 | Thanks. I've read the README of drupal/core-recommended too before posting. But still I don't get why using this would be recommended if there's the very real danger of locking your project out of possibilities to use certain other libraries or modules (if you don't switch to drupal/core). A problem like this will for example arise if you use the latest version of search_api_solr in combination with drupal/core-recommended. | |
| Jul 29, 2020 at 7:55 | history | answered | leymannx | CC BY-SA 4.0 |