[wp-trac] [WordPress Trac] #43895: Organize privacy functions into logical files and classes

[WordPress Trac]

#43895: Organize privacy functions into logical files and classes
-------------------------------------------+-----------------------
 Reporter:  iandunn                        |       Owner:  desrosj
     Type:  enhancement                    |      Status:  assigned
 Priority:  normal                         |   Milestone:  5.3
Component:  Privacy                        |     Version:  4.9.6
 Severity:  normal                         |  Resolution:
 Keywords:  early has-patch needs-testing  |     Focuses:
-------------------------------------------+-----------------------

Comment (by birgire):

 Replying to [comment:44 garrett-eclipse]:
 > Question: Should we take this opportunity to rename somethings properly.
 Speaking specifically of removal vs. erasure.
 > For example - WP_Privacy_Data_Removal_Requests_List_Table
 > Should we be updating them to the more appropriate erasure verbiage?
 > WP_Privacy_Data_Erasure_Requests_List_Table
 >
 > For context, Erasure is the more appropriate term as a users content is
 erased (anonymized or removed) and not always removed as a removal also
 entails a user deletion which the tools don't currently support.
 >
 > Thoughts? If it makes sense and doesn't have high back-compat overhead
 I'll create a patch.

 Good question.

 Since we are already deprecating the
 {{{WP_Privacy_Data_Removal_Requests_Table}}} class, now would be a good
 time to do this.

 I'm in favor of it, if there are no obvious complications, since the
 {{{erase}}} vs {{{remove}}} case can sometimes be confusing:

 One question that comes to mind if we would need to deprecate the current
 {{{WP_Privacy_Data_Removal_Requests_List_Table}}} class, in trunk, if it
 hasn't been a part of any shipped version yet?

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/43895#comment:46>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform