Seed data doesn't indicate that the format.date and format.time library settings are deprecated

Bug #1848398 reported by Jane Sandberg
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Evergreen
Confirmed
Medium
Unassigned

Bug Description

Migration #1046 changed the label for the format.date ou setting from "Format Dates with this pattern." to "Deprecated: Format Dates with this pattern." (and similarly for format.time).

However, the Deprecated: prefix never made it into the seed data, so new systems don't show these settings as deprecated.

Revision history for this message
Shula Link (slink-g) wrote :

Confirmed that the label change does not exist in the seed data.

Changed in evergreen:
status: New → Confirmed
Revision history for this message
Shula Link (slink-g) wrote :

Will this require correction in the i18n seed values as well?

Revision history for this message
Shula Link (slink-g) wrote :
tags: added: pullrequest
Revision history for this message
Jeff Davis (jdavis-sitka) wrote :

Is format.date actually deprecated? I understand that's the intention from bug 1691237, but it looks like eg-date-input still uses it. Maybe the setting is retrieved but ignored?

Revision history for this message
Shula Link (slink-g) wrote :

From what I could tell, it looks like there's a second label that specifies the yyyy-MM-dd format for format.date, as opposed to the label marked as deprecated which does not actually specify a date format.

Changed in evergreen:
milestone: none → 3.6.1
tags: added: cleanup
Changed in evergreen:
milestone: 3.6.1 → 3.6.2
Changed in evergreen:
milestone: 3.6.2 → 3.6.3
Changed in evergreen:
milestone: 3.6.3 → 3.6.4
Changed in evergreen:
milestone: 3.6.4 → 3.7.2
Changed in evergreen:
milestone: 3.7.2 → 3.7.3
Revision history for this message
Jason Boyer (jboyer) wrote :

Having looked at the current state of things The old format.date setting (I didn't bother to look for the time one) is still in use in the AJS client in at least offline.js and the ui service. The startup service uses the new settings.

What would be better than marking them deprecated in the seed data would be to complete the conversion to use the new settings everywhere, rename them in an upgrade script one more time if 'Deprecated:' isn't there, add a release note stating that they're no longer used and can be removed by admins at any time, and just remove them from the seed data altogether since no clients will use them going forward. This leaves them in existing databases if you're using them in local customizations, but there's no point in adding completely unused settings in new databases regardless of their name.

no longer affects: evergreen/3.6
Changed in evergreen:
milestone: 3.7.3 → none
Revision history for this message
Jason Boyer (jboyer) wrote :

Since I suggested it: https://git.evergreen-ils.org/?p=working/Evergreen.git;a=shortlog;h=refs/heads/user/jboyer/lp1848398_fare_thee_well_format / working/user/jboyer/lp1848398_fare_thee_well_format

Does what I said above; move all AndularJS use of format.date to webstaff.format.dates (and I didn't see any use of format.time so that was a whole lot of nothing), remove the settings entirely from seed data, and set their deprecated-ness one last time if they have been missed in the past. Includes a release note telling admins they can remove them whenever they like, but they're left in place just in case they may be in use in a local customization.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.