Skip to content

feat: show existing recordings on materials page#8102

Merged
rjsparks merged 8 commits intoietf-tools:mainfrom
holloway:view-recordings
Nov 6, 2024
Merged

feat: show existing recordings on materials page#8102
rjsparks merged 8 commits intoietf-tools:mainfrom
holloway:view-recordings

Conversation

@holloway
Copy link
Copy Markdown
Contributor

@holloway holloway commented Oct 28, 2024

See #8084

This shows existing recordings on materials page

existing recordings, on materials page
Screenshot from 2024-10-29 08-46-59

Comment thread ietf/templates/meeting/session_details_panel.html
@codecov
Copy link
Copy Markdown

codecov Bot commented Oct 28, 2024

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 88.90%. Comparing base (c7f6bde) to head (1fb6777).
Report is 133 commits behind head on main.

Additional details and impacted files
@@            Coverage Diff             @@
##             main    #8102      +/-   ##
==========================================
+ Coverage   88.78%   88.90%   +0.11%     
==========================================
  Files         296      304       +8     
  Lines       41320    41351      +31     
==========================================
+ Hits        36687    36763      +76     
+ Misses       4633     4588      -45     

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

{% endif %}
{% endfor %}
{% endif %}
{% if session.session_recording_url %}
Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Move this out of the with.

Putting the meetecho recording name directly on session is very new, and stands independent of whether there are any documents of type recording associated with the session.

<td>
<a href="{{ session.session_recording_url }}">
<i class="bi bi-file-slides"></i>
{% if 'https://meetecho-player.ietf.org/' in session.session_recording_url %}
Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Good futureproofing, but the literal should come out of settings. Currently the configuration looks like input for interpolation:

MEETECHO_SESSION_RECORDING_URL = "https://meetecho-player.ietf.org/playout/?session={session_label}"

I suggest either changing settings.py to

MEETECHO_PLAYER_URL = "https://meetecho-player.ietf.org"
MEETECHO_SESSION_RECORDING_URL = MEETECHO_PLAYER_URL+"/playout/?session={session_label}"

and then chainging this if to be

{% if settings.MEETECHO_PLAYER_URL in session.session_recording_url %}

or backing the complexity out altogether as YNGNI (when we have something else coming out of the session_recording_url function, this code will likely need to be touched again anyhow).

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

after typing all that, I lean pretty strongly towards saying remove the if and always say Meetecho until we have a need to say otherwise.

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Concur re: leaving it out.

@holloway
Copy link
Copy Markdown
Contributor Author

holloway commented Nov 5, 2024

@rjsparks @jennifer-richards any more changes needed on this PR?

@rjsparks rjsparks merged commit 5348aef into ietf-tools:main Nov 6, 2024
@rjsparks
Copy link
Copy Markdown
Member

rjsparks commented Nov 6, 2024

@rjsparks @jennifer-richards any more changes needed on this PR?

No - sorry it took so long to merge

@github-actions github-actions Bot locked as resolved and limited conversation to collaborators Nov 10, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants