Follow-up pass for renaming Usage Ping/Data to Service Ping/Data
requested to merge 334569-follow-up-pass-for-renaming-usage-ping-data-to-service-ping-data into master
What does this MR do?
Related to #334569 (closed)
- usage_ping_or_data = /(usage)[ _-]?(?:ping|data)/i # Usage Ping, usage-ping, usage_ping, Usage Data...
We need to replace instances of usage_ping_or_data
with "service". This MR handles the leftover instances that were not updated in the first passes. We are not renaming some backend services, and references to the database (and some generated HTML ids).
- Update FE symbol names
- Fix doc references to renamed files, as the old links threw 404s (e.g.
app/services/submit_usage_ping_service.rb
toapp/services/service_ping/submit_service.rb
) - Update new doc references (redirects were working fine)
Does this MR meet the acceptance criteria?
Conformity
-
I have included changelog trailers, or none are needed. (Does this MR need a changelog?) -
I have added/updated documentation, or it's not needed. (Is documentation required?) -
I have properly separated EE content from FOSS, or this MR is FOSS only. (Where should EE code go?) -
I have self-reviewed this MR per code review guidelines. -
This MR does not harm performance, or I have asked a reviewer to help assess the performance impact. (Merge request performance guidelines) -
I have followed the style guides. -
This change is backwards compatible across updates, or this does not apply.
Availability and Testing
-
I have added/updated tests following the Testing Guide, or it's not needed. (Consider all test levels. See the Test Planning Process.) -
I have tested this MR in all supported browsers, or it's not needed. -
I have informed the Infrastructure department of a default or new setting change per definition of done, or it's not needed.
Edited by Axel García