Repository navigation
Document jsondb-core 1.1.63 - #9
Merged
Merged
Conversation
Bump the current version, drop the warnings about the 1.1.16 bugs that 1.1.63 fixes, and document setSyncFolderOnWrite and the JsonDBException now thrown when a write can't be saved.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Updates the site for jsondb-core 1.1.63, the version on Maven Central since 2026-11-18.
Where to look
Review closely
src/content/docs/guides/jsondbtemplate.md: new "Surviving a crash" section. Check the claims: writes are flushed before the rename; a returned write can still be lost on a power cut unlesssetSyncFolderOnWrite(true)is on; and folder sync has no effect on Windows. The last one comes from theJsonWriter.syncDirectoryjavadoc.src/content/docs/guides/crud.md: a new paragraph says any write that can't be saved throwsJsonDBExceptionand leaves the collection unchanged. The 1.1.16 misspelt-name warning becomes one sentence.src/content/docs/reference/upgrading.md:JsonDBExceptionbullet now covers 1.1.63's new cases;src/content/docs/guides/documents.md: documents inserted without an id are stored under a random UUID, but the object you pass keeps itsnullid.Skim
guides/file-change-listeners.md,start/quick-start.mdx: the 1.1.16 warnings are removed.Safe to skip
index.mdx(the pill and both snippets);installation.mdx;astro.config.mjs(the Javadoc link, which returns 200);xpath-cheatsheet.mdand theCodeAndFile.astrocomment (both are claims that the code was run against this version; see below).How it was checked
io.jsondb:jsondb-core:1.1.63from Maven Central. This used the same scratch harness as New documentation site: Astro + Starlight, indigo theme, new icon #8 (not committed), compiled with--release 8, and all 129 checks pass.setSyncFolderOnWrite;JsonDBException, with no change in memory or on disk and no.tmpfile left;users.jsonoutput is byte-for-byte the same in 1.1.63.npm run buildpasses, and the links validator reports all internal links valid, anchors included.What this does not do
ERROR io.jsondb.io.JsonWriter - Failed to create temporary file for collection userswith a stack trace, then throws. That looks like ajsondb-coreissue, so the site says nothing about it either way.JsonWriter.renameKeyInJsonFile()andUtil.setFieldValueForEntity()). The site never documented either method.