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

feature/robust-cache-messages #455

Open
wants to merge 2 commits into
base: main
Choose a base branch
from

Conversation

BrianWhitneyAI
Copy link
Contributor

Description

The purpose of this PR is to resolve #417 and clear up some misleading reporting about the cache action. This PR separates the net success message into two separate messages for the two condition (while keeping messages separate). it also handles plural/singular cases.

@BrianWhitneyAI BrianWhitneyAI marked this pull request as ready for review February 27, 2025 20:47
@BrianWhitneyAI
Copy link
Contributor Author

Screenshot 2025-02-27 at 12 42 23 PM

const file = fileDetails.find((f) => f.id === fileId);
const isAlreadyCached = file?.annotations.some(
({ name, values }) =>
name === "Should Be in Local Cache" && values[0] === true
Copy link
Contributor

Choose a reason for hiding this comment

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

we might want to use the AnnotationName.SHOULD_BE_IN_LOCAL constant here and elsewhere (saw that the full string is also used in other places) if possible

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.

Copy to VAST success message is misleading when extending expiration dates
4 participants