You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
A follow-on to #1367 - at some point, it would be a good idea to go through the code base and change everything currently referring to "office" and "offices" -> "service"/"services"
In the long run, this will save developer time, both for on-boarding, but also for people not having to check whether any particular variable/property is called office or service.
This will necessitate a number of changes to our models - the Office model will need to be renamed Service and the .office property of BaseChant will need to be renamed .service.
The text was updated successfully, but these errors were encountered:
… use 'service' instead of 'office'.
- change all URL paths to use 'service/services'. DDMAL#1401
- create redirects to ensure backwards compatibility with old 'office/offices' URLs. DDMAL#1401
- update query parameters to use 'service' instead of 'office'. DDMAL#1401
- rename the Office model to Service. DDMAL#1402
- rename .office property of BaseChant to .service. DDMAL#1402
- change all instances of 'office' to 'service' in the codebase. DDMAL#1402
- update all references to 'office' to 'service' on the Django admin pages. DDMAL#1581
A follow-on to #1367 - at some point, it would be a good idea to go through the code base and change everything currently referring to "office" and "offices" -> "service"/"services"
In the long run, this will save developer time, both for on-boarding, but also for people not having to check whether any particular variable/property is called
office
orservice
.This will necessitate a number of changes to our models - the
Office
model will need to be renamedService
and the.office
property of BaseChant will need to be renamed.service
.The text was updated successfully, but these errors were encountered: