Skip to content

Dev-328: View previous semesters offered #478

Open
trickfu wants to merge 3 commits intopreviewfrom
view-sem
Open

Dev-328: View previous semesters offered #478
trickfu wants to merge 3 commits intopreviewfrom
view-sem

Conversation

@trickfu
Copy link
Copy Markdown
Contributor

@trickfu trickfu commented Apr 1, 2026

References

  • Linear: DEV-328 sub-issue

Proposed Changes

  • added an api endpoint in backend > hoagieplan > api > dashboard > details.py because prior I think it would only return the most recent term from guid. I added this so now it records ALL prior terms that are in the DB

  • in the front end I added the module to fit the italics text and actually display

  • i have it display previous terms offered including the current one like spring 2026

  • miscellaneous I thought this was adding the semester tag in previous commits but realized that was another task. I have removed my additions for semester tag :)

@linear
Copy link
Copy Markdown

linear bot commented Apr 1, 2026

@vercel
Copy link
Copy Markdown

vercel bot commented Apr 1, 2026

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Actions Updated (UTC)
plan Ready Ready Preview, Comment Apr 1, 2026 4:28am

Request Review

@trickfu trickfu changed the title Dev-328 View previous semesters offered Dev-328: View previous semesters offered Apr 1, 2026
</div>
)}
</div>
{prevTerms.length > 0 && <div className={styles.prevTerms}>{prevTerms.join(', ')}</div>}
Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

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

Are we using the .svg files?

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

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

no sorry I added these because I previously thought my task was to display the semester tags. I can remove these when I fix this pr. I'll get this fix in when I get clarification on how I should approach DashboardSearchItem firing a separate backend request

Copy link
Copy Markdown
Collaborator

@issacli-0821 issacli-0821 Apr 1, 2026

Choose a reason for hiding this comment

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

Right now, each DashboardSearchItem is firing a separate backend request. This would be bad for large queries (for example, look at the network requests under the developer console when you query 'c' in the search bar). Not sure what the best way to do this is, but one idea is to do these queries in DashboardSearchResults or Canvas

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

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

I think that if we were to do these in the initial search for the terms, the time it takes for the cards to load would increase. Having a quick loading for the cards then this happening next felt like it made sense, but I also understand the issue with a separate backend request. I can try to do that if we believe that would be better.

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

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

Let's try doing it in the initial search and see if we can make it fast enough. If we can't, then we can discuss what the alternative is.

@issacli-0821 issacli-0821 requested a review from emiilyyou April 1, 2026 21:30
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