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.
- First commit to issue fork.
- Merge request !11558Issue #3161684: Use API instead of http requests to setup language negotiation β (Open) created by acbramley
- π¦πΊAustralia acbramley
This was a little tricky to figure out, I had to manually do the steps in a browser and export config before/after to figure out what needed to change (IS was inaccurate)
- πΊπΈUnited States smustgrave
Are we limiting to just that 1 file? Could that be marked in the summary.
Checking that 1 file could we do more replacements with the drupalCreateNode?
- π¦πΊAustralia acbramley
Rescoping to just NodeFieldMultilingualTest, other tests can be separate issues (e.g π NodeTranslationUITest should use API to set up language Active )
We shouldn't replace the node form submissions because the test is literally testing language functionality of the node form :)
- π§πͺBelgium borisson_ Mechelen, π§πͺ
This looks great and it makes this test a bit faster.