- πΊπΈUnited States smustgrave
Thank you for creating this issue to improve Drupal.
We are working to decide if this task is still relevant to a currently supported version of Drupal. There hasn't been any discussion here for over 8 years which suggests that this has either been implemented or is no longer relevant. Your thoughts on this will allow a decision to be made.
Since we need more information to move forward with this issue, the status is now Postponed (maintainer needs more info). If we don't receive additional information to help with the issue, it may be closed after three months.
- Status changed to Closed: outdated
3 months ago 4:04pm 18 April 2025 - πΊπΈUnited States smustgrave
Since there has been no follow up in 3 months going to close out. But don't worry this can always be re-opened!
Thanks
- Status changed to Active
21 days ago 1:40am 6 July 2025 - πΊπΈUnited States xjm
They're still there and haven't been clarified. :)
- π¦πΊAustralia acbramley
We still need more information, I agree with #1 that the comments are a bit superfluous as they're just stating what happens when you save a node with a langcode. Unless we want to heavily document what a fallback is in the test (I don't think we should) maybe we should just remove the entire comment, or just make it "Creating a public node with langcode Hungarian"
We should also update the IS with the exact comments we want to change (remove the original report) and update the proposed resolution.
- πΊπΈUnited States xjm
I don't think PMNMI is the correct status? We just need proposals for better comments. (Another node-access-not-actually-node issue.) It's tagged "Needs IS update", which corresponds to "Active" when there's no MR (or NW when there is one). Thanks!
- πΊπΈUnited States xjm
Aside: This issue is what happens when we descope the docs gate from something!!
- πΊπΈUnited States xjm
One of the issues with the comments is grammar. They're not grammatically correct English.
I think it is relevant to document which langcode behavior we expect to use as that is the biggest gotcha of the whole API (and also exactly what is under test).
That said, the fact that this comment is repeated N times also hints at possible refactorings. (Out of scope, but might make the test easier to follow and reduce the need for boilerplate docs since helper methods or data providers would be more self-documenting.)