fix: Use session.order_in_meeting() in the agenda #5222
Merged
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.
Updates the
preprocess_assignments_for_agenda()
helper method to useorder_in_meeting()
to assignsession.order_number
. This is more stable and agrees with what thesession_details()
meeting view and thegroup.views.meetings()
view do.FYI, for the preliminary IETF-116 agenda, the following sessions change number. The data being diffed are
[group acronym, session name, order_number]
from the JSON data used to construct the agenda display.<
are "before" and>
are after. Most changes are to breaks/etc that do not have meetecho sessions anyway.