- Issue created by @Liam Morland
- First commit to issue fork.
- Status changed to Needs review
almost 2 years ago 2:54pm 14 March 2023 - 🇮🇳India Ranjit1032002
I have created a patch for the issue mentioned, please review.
Thank You. - Status changed to Needs work
almost 2 years ago 4:12pm 15 March 2023 - 🇨🇦Canada Liam Morland Ontario, CA 🇨🇦
This should only change the deprecation message. It should not rename any functions.
- Status changed to Needs review
almost 2 years ago 4:27am 16 March 2023 - Status changed to Needs work
almost 2 years ago 6:50am 16 March 2023 - 🇺🇸United States smustgrave
Nevermind the changes to node.module were incorrect. But still appears there needs to be a fix to node.module deprecation message. #6 is just updating a test file.
- First commit to issue fork.
- @rassoni opened merge request.
- 🇨🇦Canada Liam Morland Ontario, CA 🇨🇦
The point of
testNodeRevisionLoadDeprecation()
is to test that whennode_revision_load()
is called, a deprecation notice is generated.The only changes this needs is the to the contents of the deprecation notice.
- last update
over 1 year ago 29,279 pass, 1 fail - last update
over 1 year ago 29,260 pass, 2 fail - last update
over 1 year ago Custom Commands Failed - last update
over 1 year ago Custom Commands Failed - last update
over 1 year ago 29,283 pass - last update
over 1 year ago 29,283 pass - last update
over 1 year ago 29,283 pass - Status changed to Needs review
over 1 year ago 11:02am 18 April 2023 - last update
over 1 year ago 29,283 pass - 🇧🇷Brazil elber Brazil
Hi I removed the message to updateType() method because it is not belongs a RevisionableStorageInterface.Please revise.
- last update
over 1 year ago 29,283 pass - Status changed to RTBC
over 1 year ago 3:55pm 19 April 2023 - 🇺🇸United States smustgrave
Going to mark this but there's 1 NIT pick that could be fixed at commit.
- last update
over 1 year ago 29,300 pass - last update
over 1 year ago 29,302 pass - last update
over 1 year ago 29,304 pass - last update
over 1 year ago 29,359 pass - last update
over 1 year ago 29,366 pass -
longwave →
committed 0dc53e4f on 10.1.x
Issue #3345272 by Rassoni, elber, Ranjit1032002, Rishabh Vishwakarma,...
-
longwave →
committed 0dc53e4f on 10.1.x
- Status changed to Fixed
over 1 year ago 6:17pm 30 April 2023 - 🇬🇧United Kingdom longwave UK
Thanks @smustgrave - skipped the blank line change on commit.
Committed and pushed 0dc53e4f69 to 10.1.x. Thanks!
Automatically closed - issue fixed for 2 weeks with no activity.