fix: Use session name instead of timeslot name on agenda #5086
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Fixes #4457.
This uses the session name instead of the timeslot name to label special (
type != "regular"
) sessions on the meeting agenda. The timeslot name is used for regular session headings ("Session I", "Session II", etc). This allows the agenda to be updated using the "Edit session" links from the schedule editor.Changes the rendered agendas for some existing meetings. Includes a data migration to replace
Session.name
withTimeSlot.name
for all non-'regular' sessions of IETF meetings except meetings 91-98. The meetings in that range had more descriptive names on theSession
instances. I have not exhaustively compared meeting agendas, but all the agendas I examined looked the same or better with these updates.A list of the session names that changed on my dev instance:
session-names.csv
The old session names are labeled
session.name
in the file. The new names are labeled timeslot.name.