Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Scc 4142/spec coll messaging #421

Open
wants to merge 45 commits into
base: special-collections
Choose a base branch
from

Conversation

charmingduchess
Copy link
Contributor

@charmingduchess charmingduchess commented Dec 17, 2024

This is a preliminary refactor to facilitate this ticket. Would love some eyes on this before I go all the way down this path.
To summarize, I created an ItemAvailability model which builds a string that represents it's availability, location, and special collections status. The model also handles returning the correct message component.

Ticket:

  • JIRA ticket xxx

This PR does the following:

How has this been tested?

Accessibility concerns or updates

Checklist:

  • I updated the CHANGELOG with the appropriate information and JIRA ticket number (if applicable).
  • I have added relevant accessibility documentation for this pull request.
  • All new and existing tests passed.

Copy link

vercel bot commented Dec 17, 2024

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name Status Preview Comments Updated (UTC)
research-catalog ✅ Ready (Inspect) Visit Preview 💬 Add feedback Dec 24, 2024 3:16pm

Copy link
Contributor

Choose a reason for hiding this comment

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

Is there a reason this functionality needs its own class? I feel like the key building could be added to the item model with a component handling the presentation logic.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

it's so focused on a specific cluster of data that I think it justifies its own class. I am going to move the presentation logic to the component.

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.

3 participants