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
My local server and efile-test have the same versions for court 0 and court dupage; only 0 seems to have the datafieldconfig zip anymore. However, on efile-test all of the configs for each court, including dupage, are still in the table.
This actually helped hide a bug that was only partially fixed in 593d547, but shows up locally.
The whole thing means that if a genericode zip just stops existing, we won't delete it's data, which will lead to stale configs if the parent courts ever change anything.
The text was updated successfully, but these errors were encountered:
My local server and
efile-test
have the same versions for court0
and courtdupage
; only 0 seems to have the datafieldconfig zip anymore. However, onefile-test
all of the configs for each court, includingdupage
, are still in the table.This actually helped hide a bug that was only partially fixed in 593d547, but shows up locally.
The whole thing means that if a genericode zip just stops existing, we won't delete it's data, which will lead to stale configs if the parent courts ever change anything.
The text was updated successfully, but these errors were encountered: