We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
We’ve got FreshnessChecker that uses app-provided policy on when to serve cached code.
FreshnessChecker
We should also mark code that’s crashed as non-fresh. That way if ever we do a bad release, the user won’t be stuck with a bad build.
The text was updated successfully, but these errors were encountered:
No branches or pull requests
We’ve got
FreshnessChecker
that uses app-provided policy on when to serve cached code.We should also mark code that’s crashed as non-fresh. That way if ever we do a bad release, the user won’t be stuck with a bad build.
The text was updated successfully, but these errors were encountered: