Closed (fixed)
Project:
Drupal core
Version:
8.0.x-dev
Component:
base system
Priority:
Normal
Category:
Task
Assigned:
Unassigned
Issue tags:
Reporter:
Created:
3 Jul 2014 at 18:14 UTC
Updated:
29 Jul 2014 at 23:43 UTC
Jump to comment: Most recent, Most recent file
Comments
Comment #1
LinL commentedLooks good.
Comment #2
LinL commentedLooking again, does this need a change record?
Moving back to Needs review.
Comment #3
marcingy commentedMost items that do removal seem to be going in without a change record, so not sure what the rule is to be honest...
Comment #4
ianthomas_ukAny API that exists in Drupal 7 but not in Drupal 8, or has changed, should be covered by a change record. The core maintainers may not always spot when a change record is needed, but that doesn't mean we should be encouraging patches to be committed without appropriate change records.
We should also update any other change records that refer to check_plain.
https://www.drupal.org/list-changes/published?keywords_description=check...
Comment #5
marcingy commentedAs I say most deprecated functions are not getting change records on removal, so lets get a policy in place for doing rather than randomly selecting an issue as this one has been. Unassigning and unfollowing.
Comment #6
pushpinderchauhan commentedAs all usage of check_plain() function already removed from repository, so now we can also remove this function from bootstrap.inc file.
Please review the attached patch as above patch is unable to apply.
Comment #7
ParisLiakos commentedgrep couldnt find anything else than the function itself
Comment #8
webchickThanks for the change record. Since this is one of the top most-used functions in D7, I expanded the title a bit to explicitly include the name of the functions there so people can find it easily.
Committed and pushed to 8.x. Thanks!