The Needs Review Queue Bot → tested this issue. It either no longer applies to Drupal core, or fails the Drupal core commit checks. Therefore, this issue status is now "Needs work".
Apart from a re-roll or rebase, this issue may need more work to address feedback in the issue or MR comments. To progress an issue, incorporate this feedback as part of the process of updating the issue. This helps other contributors to know what is outstanding.
Consult the Drupal Contributor Guide → to find step-by-step guides for working with issues.
- Status changed to Needs review
3 months ago 4:18pm 24 September 2024 - 🇬🇧United Kingdom rachel_norfolk UK
Marking as Needs Review by a budding first time contributor at DrupalCon...
- 🇺🇸United States smustgrave
Thanks for picking up! And hope DrupalCon barcelona is going well!
So issues should follow the standard issue template (can find it by creating a new issue and copying that summary)
Also fixes should be in MRs vs patches so that tests may run.
Feel free to keep working just marking with the DrupalCon message.
Novice issue reserved for the Mentored Contribution during DrupalCon Barcelona 2024. After the 27th of September 2024, this issue returns to being open to all. Thanks
- First commit to issue fork.
- 🇬🇧United Kingdom jacobupal Leeds
This needs to be reviewed by somebody who knows fields because now the patches have been re-rolled and turned into a merge request we can't actually confirm that the the types and identifiers present in the annotation are correct or correspond correctly with the associated field types.
I'm also removing the novice tag, as this has moved far beyond novice!
- 🇺🇸United States smustgrave
Issue summary should probably be updated some as template appears to be incomplete and maybe missing some relevant sections from the default issue summary template.