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
{{ message }}
This repository has been archived by the owner on Apr 29, 2019. It is now read-only.
show_request() currently has a small algorithm for trying to fix the SR# if it can't find the one originally asked for (strip it to just numbers and, depending on length, prefix with the current year and add the dash after the first two digits). This is specific to Chicago (and most Motorola CSR-based systems). This should be a more generic, pluggable systems so that can work for other cities.
The text was updated successfully, but these errors were encountered:
tacaswell
added a commit
to tacaswell/srtracker
that referenced
this issue
Jan 16, 2013
First pass at factoring out the code that fixes the up failed service
request-id.
The Chicago specific code has been moved to fix_request_id_chi, which
is assigned to fix_request_id, which is the function that is actually
called in show_request(). Any other cities need to write an
equivalent to fix_request_id_chi and assign it to fix_request_id
(presumably, there is a way to make this more pluggable/configurable).
show_request() currently has a small algorithm for trying to fix the SR# if it can't find the one originally asked for (strip it to just numbers and, depending on length, prefix with the current year and add the dash after the first two digits). This is specific to Chicago (and most Motorola CSR-based systems). This should be a more generic, pluggable systems so that can work for other cities.
The text was updated successfully, but these errors were encountered: