Remove last literal mentions of the old project name (AI)
cache.js's comment explaining the DB_NAME prefix change referenced the old "cmjs-" prefix literally as a historical note. Reworded to describe the effect generically instead, so no trace of the former project name remains anywhere in the repo. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
This commit is contained in:
1 parent
16395fa7c5
commit
91a24574a8
1 file changed
+5
-7
+5
-7
@@ -12,13 +12,11 @@
|
||||
// each file's mtime happens to change — which, on a "deploy and forget"
|
||||
// site, could be years.
|
||||
const CACHE_SCHEMA_VERSION = 3;
|
||||
// The `cmjs-` -> `cmkiss-` prefix change (project rename) already has the
|
||||
// same effect as a version bump would — every existing visitor's browser
|
||||
// opens a fresh, empty database under the new name, and the old
|
||||
// `cmjs-cache-v3` one is left behind as orphaned storage (harmless; this
|
||||
// module degrades to live-fetch behaviour whenever the cache is empty or
|
||||
// unavailable). Deliberate, one-time, not something to repeat — don't bump
|
||||
// CACHE_SCHEMA_VERSION for this same reason again.
|
||||
// Renaming this prefix has the same effect as a version bump would — every
|
||||
// existing visitor's browser opens a fresh, empty database under the new
|
||||
// name, and the previous one is left behind as orphaned storage (harmless;
|
||||
// this module degrades to live-fetch behaviour whenever the cache is empty
|
||||
// or unavailable). Do this deliberately, not casually.
|
||||
const DB_NAME = `cmkiss-cache-v${CACHE_SCHEMA_VERSION}`;
|
||||
const STORE_NAME = 'articleFiles';
|
||||
|
||||
|
||||
Reference in new issue
Block a user