Skip to content

Conversation

@pjaudiomv
Copy link
Collaborator

I'm not sure if there is a way to do this already or not but with larger datasets I had a desire to have the meetings page load on the current day and just show that days meetings (less scrolling). Not sure how people feel about it but seemed like easy enough change so here it :)

@pjaudiomv pjaudiomv requested a review from joshreisner November 4, 2025 00:54
@netlify
Copy link

netlify bot commented Nov 4, 2025

Deploy Preview for tsml-ui ready!

Name Link
🔨 Latest commit 427701b
🔍 Latest deploy log https://app.netlify.com/projects/tsml-ui/deploys/690a4ab61d2b4100080e6ec1
😎 Deploy Preview https://deploy-preview-485--tsml-ui.netlify.app
📱 Preview on mobile
Toggle QR Code...

QR Code

Use your smartphone camera to open QR code link.

To edit notification comments on pull requests, go to your Netlify project configuration.

@joshreisner
Copy link
Contributor

also more scrolling in a way, since you need to scroll past all the elapsed meetings in the list to see the next ones

but this option makes sense to me in principle, since TSML had "today" behavior with an tsml-time=upcoming param, so this is the reverse of that

@pjaudiomv
Copy link
Collaborator Author

also more scrolling in a way, since you need to scroll past all the elapsed meetings in the list to see the next ones

but this option makes sense to me in principle, since TSML had "today" behavior with an tsml-time=upcoming param, so this is the reverse of that

ya it would be better to have current (in time) meetings first and rest "rollover" to end.

@joshreisner
Copy link
Contributor

idk about rolling over - it's good also to keep the list chronological. i think if it did roll over we'd need some kind of visual separator

anyway, just had one minor comment but otherwise lgtm, thanks!

@pjaudiomv
Copy link
Collaborator Author

idk about rolling over - it's good also to keep the list chronological. i think if it did roll over we'd need some kind of visual separator

anyway, just had one minor comment but otherwise lgtm, thanks!

yes your right, it def would be confusing without some sort of separator or something

@joshreisner joshreisner merged commit d06d75f into code4recovery:main Nov 5, 2025
6 checks passed
@pjaudiomv pjaudiomv deleted the pj/feat-weekday-today-parameter branch November 5, 2025 01:38
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants