Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Cleanup: rename "Incident Reports" as "Field Reports" #1469

Closed
srabraham opened this issue Dec 20, 2024 · 1 comment
Closed

Cleanup: rename "Incident Reports" as "Field Reports" #1469

srabraham opened this issue Dec 20, 2024 · 1 comment
Assignees
@srabraham

Comments

@srabraham
Copy link
Member

srabraham commented Dec 20, 2024 •
edited
Loading

I did a surface level rename of "Incident Reports" to "Field Reports" last month, so as far as users are concerned, the migration is already done. See #371 and #1378

This issue is about pushing that rename through the rest of the system, i.e. through all the web client code, the API, the server code, and (maybe eventually) the database.

I've pretty much finished moving over the web client code at this point, via #1466 #1467 #1468 #1470

Next up is the API layer
@srabraham srabraham self-assigned this Dec 20, 2024
srabraham added a commit that referenced this issue Dec 20, 2024
@srabraham
almost finish the web client migration to "Field Reports"
882c0ab 
this leaves some API references (via _url.py) as the only remaining
bits of "incident report" usage in the legacy web client

#1469
@srabraham srabraham mentioned this issue Dec 20, 2024
Merged
srabraham added a commit that referenced this issue Dec 20, 2024
@srabraham
almost finish the web client migration to "Field Reports"
303137d 
this leaves some API references (via _url.py) as the only remaining
bits of "incident report" usage in the legacy web client

#1469
srabraham added a commit that referenced this issue Dec 20, 2024
@srabraham
rename "incident report" to "field report" in API and auth
3b9932e 
#1469
@srabraham srabraham mentioned this issue Dec 20, 2024
Merged
srabraham added a commit that referenced this issue Dec 20, 2024
@srabraham
rename "incident report" to "field report" in API and auth
1fd9c22 
#1469
srabraham added a commit that referenced this issue Dec 21, 2024
@srabraham
continue the rename of "incident report" to "field report"
ad3ed00 
this takes us most of the way down to the persistence layer

#1469
@srabraham srabraham mentioned this issue Dec 21, 2024
Merged
srabraham added a commit that referenced this issue Dec 21, 2024
@srabraham
continue the rename of "incident report" to "field report"
3dc0fc0 
this takes us most of the way down to the persistence layer

#1469
@srabraham srabraham mentioned this issue Dec 21, 2024
Merged
srabraham added a commit that referenced this issue Dec 21, 2024
@srabraham
do some final little bits of "field report" renaming
0401680 
now I really think we're just down to the database level

#1469
@srabraham srabraham mentioned this issue Dec 21, 2024
Merged
srabraham added a commit that referenced this issue Dec 21, 2024
@srabraham
do some final little bits of "field report" renaming
581f0fe 
now I really think we're just down to the database level

#1469
@srabraham
Copy link
Member Author

alright, all that's left is to alter the schemas

https://github.com/search?q=repo%3Aburningmantech%2Franger-ims-server+%2Fincident%5B%5E.%28%5D%3Freport%2F&type=code

srabraham added a commit that referenced this issue Jan 2, 2025
@srabraham
complete the "Field Report" migration 🎉🎉🎉
48e6a77 
This moves over the persistence layer from the old "Incident Report"
name, and this is the last of that extensive migration.

#1469
@srabraham srabraham mentioned this issue Jan 2, 2025
Merged
srabraham added a commit that referenced this issue Jan 2, 2025
@srabraham
complete the "Field Report" migration 🎉🎉🎉
00feaf3 
This moves over the persistence layer from the old "Incident Report"
name, and this is the last of that extensive migration.

#1469
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@srabraham srabraham

Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@srabraham