JSONC (JSON with comments) converts to standard JSON as a new input-only format: hand-written parser, comments and trailing commas removed at the same offsets, token-level output that keeps every number and key as written. Input-only formats in the framework (meta.inputOnly), reverse errors with line/column, JSONC editor highlighting and lint, a one-click hint in the JSON → direction, strings in four locales, docs and the 2.1.0 version bump.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Cloudflare's Rate Limiting binding checks a locally cached count per edge
machine and syncs it in the background. On production one keep-alive
connection hits the limits almost exactly (120 pages, then 429s), but 300
requests on fresh parallel connections in 13 s all passed. Say so in
DEPLOYMENT.md and the rate-limit.ts header instead of "overshoot slightly",
and document a one-connection curl test for production.
Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
The Worker now runs first for every request except the content-hashed
bundles under /assets/ (run_worker_first: ["/*", "!/assets/*"]) and counts
it against a per-client limit before serving it:
- SITE_LIMITER: pages and public files, 120 requests / 60 s
- API_LIMITER: every /api/* request, 60 / 60 s
- VERIFY_LIMITER: /api/turnstile/verify on top, 30 / 60 s (unchanged)
Over the limit, pages get a plain-text 429 in the four UI languages and the
API a JSON 429 (rate_limited); both carry Retry-After: 60. Clients are keyed
on their IPv4 address or the /64 of their IPv6 address, never logged. Pages
still go through env.ASSETS.fetch(), so _headers, _redirects and the SPA
fallback apply as before. A failing limiter lets requests through. Previews
get their own counters (namespace_id 4204/4206).
Docs: DEPLOYMENT, PRIVACY (wording only, nothing new collected, no
re-consent), SECURITY, CONTRIBUTING, READMEs, CLAUDE.md, ROADMAP, CHANGELOG.
Version 2.0.2 (versionCode 20002).
Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
- The wrapper div @uiw/react-codemirror renders now fills its panel, so the input editor and the read-only output scroll with the wheel, touch and keyboard; the read-only output's scroll container is focusable (arrow/page keys) without becoming contenteditable.
- CSP (web and Tauri) allows 'wasm-unsafe-eval' for bson's WebAssembly helper; Permissions-Policy drops browsing-topics.
- Version 2.0.1 (Android versionCode 20001); CHANGELOG and docs updated.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Require the pushed commit three times in a row before checking production, and retry the header/route/API checks up to four times, 20 s apart. A deploy needs a short while to reach every Cloudflare edge location.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
- Web app moves to https://jsonprism.poli0981.dev on Cloudflare Workers
(static assets + /api/turnstile/verify + /api/health), with security
headers, redirects for the old /jsonPrism paths, previews for
non-production branches and a production smoke workflow. GitHub Pages
only redirects now.
- Web-only Turnstile human check (server-verified, 7-day pass) and
cookieless Web Analytics (after consent, opt-out, off under GPC);
Privacy Policy and Terms 2.0, consent version 2.
- Node 26, TypeScript 7 with the TS 6 API alias for typescript-eslint,
dependencies on current majors (ends the ERESOLVE that kept main red).
- Converter fixes: CSV columns, binary ZIP entries, MySQL backslash
escaping, RESX/XML validity, BSON size, YAML quoting and alias limits,
TOML nulls and big integers, JSON error positions, JSONL/BOM linting.
- Web Worker conversion, faster editor, technical UI refresh with an
Appearance menu and custom scrollbars, accessibility and i18n gaps.
- Tauri least-privilege capabilities, hardened CSP, Tauri 2.12.
- CI: SHA-pinned least-privilege workflows, SonarQube Cloud, Rust job,
verifiable releases (SHA256SUMS + provenance); Dependabot grouping.
- 864 tests (97% line coverage), SonarCloud quality gate passing; docs,
legal and CLAUDE.md refreshed.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
The v1.7.2 global link interceptor routed external URLs through
`@tauri-apps/plugin-shell`'s `open()`, but that throws on Android:
"Scoped shell IO error: No such file or directory (os error 2)" — the
shell plugin has no native URL handler on mobile, so every tapped link
did nothing. (The earlier ConsentGate per-link shell.open from #98 had
the same flaw; it was simply never tap-tested on Android.)
Switch to `@tauri-apps/plugin-opener`'s `openUrl()`, whose `open_url` has
a real cfg(mobile) split that routes to the native Intent.ACTION_VIEW
handler. Plain `openUrl(url)` — no inAppBrowser (that option regressed
os-error-2 on Android 16, plugins-workspace#2913).
Wiring: tauri-plugin-opener crate + init, @tauri-apps/plugin-opener npm,
"opener:default" capability (its allow-open-url permits any URL). Shell
plugin removed entirely (openExternal was its only consumer) — also from
vite optimizeDeps, knip ignore, and the THIRD-PARTY/TAURI-NOTES docs.
Verified on emulator API 33 (Android 13, WebView Chromium 109): tapping
the consent-gate License link and footer X link both fire ActivityManager
START ACTION_VIEW and open Chrome; no shell error.
Co-authored-by: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
Tapping any external link did nothing on the Android build: Tauri's
WebView (Android especially) silently ignores `target="_blank"`, so the
plain anchors in Header, Footer and About never opened. Only ConsentGate
had a per-link workaround (PR #98).
Replace that with one app-wide delegated click interceptor
(`useExternalLinkInterceptor`, mounted at the App root): when `isTauri()`
it catches clicks on any `a[href^=http]` and hands the URL to the system
browser via `openExternal()` / plugin-shell. The web build is untouched —
the listener is gated behind `isTauri()` so it is never installed there,
and in-app router links keep relative hrefs so they aren't intercepted
(reads `getAttribute('href')`, not the absolutising `.href` property).
Removes the now-redundant onClick handler from ConsentGate.
No Tauri/Rust/manifest/CSP changes were needed — shell:allow-open and
plugin-shell were already correct (ConsentGate proved it on Android).
Bumps version to 1.7.2 (Android versionCode 10702).
Co-authored-by: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
Bump version to 1.7.1 across package.json, lockfiles, Cargo.toml, and
tauri.conf.json (android versionCode 10700 -> 10701), and add the CHANGELOG
entry for the Android fix round (#98).
Co-authored-by: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
The Android sideload APK never showed the consent gate and the file-load
toast surfaced opaque content-URI document ids:
1. Legal gate: `consentStore` skipped the gate for ALL Tauri builds, justified
by the desktop installer's license page — which the sideload APK doesn't
have, so Android users never saw or accepted the terms. Add a build-time
`__IS_ANDROID_BUILD__` define (`TAURI_ENV_PLATFORM === 'android'`) and gate
only on desktop Tauri (`__IS_TAURI_BUILD__ && !__IS_ANDROID_BUILD__`); Android
now shows the gate like the web build. Acceptance persists in the Android
WebView's localStorage, so it asks only once.
2. Legal links: add an `openExternal()` helper that routes through
`@tauri-apps/plugin-shell` inside Tauri (web keeps `window.open`), and wire
the gate's License/Terms/Privacy/Disclaimer links to it — plain
`target="_blank"` is swallowed by the Android WebView.
3. File-load toast: when the picked name has no usable extension (opaque Android
content URIs like `msf:1000000123`), fall back to a count-based
"N file(s) loaded" via new `toast.files_loaded` keys; keep the clean
"Loaded <name>" when a real filename is available. Desktop/web are unchanged.
Also reword `consent.intro` "in your browser" -> "on your device" (accurate on
the native app). typecheck / lint / 215 tests / web build all green; verified on
the Android emulator (gate shows once, links open the system browser, toast).
Co-authored-by: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
Add a "System requirements" table to the README Android section (EN + VI):
Android 12+ (API 31), Android System WebView Chromium 111+, supported ABIs,
RAM, storage, and offline/no-network note — with guidance to update WebView
if the UI looks broken. Refresh the now-stale Android testing note in
docs/pc_spec.md (EN + VI) to reflect emulator-based build + smoke testing.
Co-authored-by: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
Bump version 1.6.1 -> 1.7.0 (Android versionCode 10700) and document the
release. Highlights: signed universal Android APK (minSdk 31), self-hosted
fonts for full offline rendering, robust SAF content-URI file open. See
CHANGELOG.md for details.
Co-authored-by: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
Add an Android target alongside the desktop bundles. Users download a signed
universal .apk and sideload it; minSdk 31 blocks Android < 12 at install time.
- tauri.conf.json: bundle.android (minSdkVersion 31, versionCode 10601)
- commit the generated src-tauri/gen/android Gradle project (source only; build
outputs + keystore stay gitignored) with release signing wired from a
gitignored keystore.properties (graceful unsigned fallback when absent)
- self-host fonts via @fontsource (drop Google Fonts <link>, tighten CSP) so the
app renders fully offline
- robust native file open: basenameFromPath() recovers a filename from Android
content:// URIs; the native-open path filters extensions leniently so opaque
MediaStore URIs the dialog already vetted are not wrongly rejected
- npm scripts tauri:android:{init,dev,build}; android job in release.yml signs
from secrets and uploads the APK to the same draft release
- docs: README/README.vi Android sections, TAURI-NOTES maintainer notes (incl.
the WebView Chromium >= 111 requirement), ROADMAP phase 7
Validated on emulators: signed APK installs on Android 12+, blocked on API < 31
(INSTALL_FAILED_OLDER_SDK), launches, renders, runs converters, reads files via
the SAF picker, fully offline. New unit tests for basenameFromPath + lenient
filterByExtension; full gate green (format/typecheck/lint/knip/215 tests).
Co-authored-by: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
Each matrix platform ran tauri-action's find-or-create-release
concurrently; with no release present yet they raced to create it,
yielding two draft releases that split the assets (Linux bundles in one,
macOS/Windows in the other). This was hit on the v1.6.1 release and had
to be reconciled by hand.
Add a `create-release` job that makes the draft release once and outputs
its id; the build matrix now `needs` it and uploads via `releaseId`
instead of each job finding/creating its own. One release, all platforms'
bundles together. The maintainer still un-drafts manually.
Co-authored-by: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
Patch release bundling the build-only changes since 1.6.0:
- Split the CodeMirror core chunk (cm-view + cm-core) so no chunk trips
Vite's 500 kB warning; migrated to Rolldown advancedChunks (#74).
- Stopped shipping source maps on the public web build (#72).
- 27 grouped npm minor/patch dependency updates (#67).
Bumps package.json, package-lock.json, src-tauri/Cargo.toml,
src-tauri/Cargo.lock, src-tauri/tauri.conf.json to 1.6.1 and moves the
CHANGELOG [Unreleased] section to [1.6.1].
Co-authored-by: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
Migrate vite.config.ts chunking from the deprecated manualChunks
function form to advancedChunks.groups. Rolldown's optimizer silently
re-merged manualChunks sub-chunks, so a cm-core split was ignored.
Split the ~614 kB cm-core into cm-view (~245 kB, the @codemirror/view
engine) + cm-core (~362 kB, state/language/lezer/@uiw); cm-langs is
unchanged (~60 kB). No chunk now exceeds Vite's 500 kB warning limit.
Same total/gzip bytes — the editor still loads all three behind its
existing React.lazy boundary, so this is finer file granularity for
better cross-deploy caching. No converter or UI behavior changed.
Verified: clean build (no warning), 209 tests pass, production preview
renders/highlights/converts with all cm-* chunks 200 OK, no console errors.
Co-authored-by: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
The web production build emitted .js.map files into dist/, and deploy.yml
uploads the whole dist/ to GitHub Pages — exposing full original source via
DevTools on the public site. Nothing consumes the maps (PRIVACY.md: no remote
error reporting), so gate them to local non-production web builds only; prod
web and Tauri now emit none.
Co-authored-by: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
- Refactor: decompose BatchPanel (515→289), ConverterWorkspace (314→206),
and InputPanel (278→216) into pure utilities, leaf components, and hooks.
Behavior-preserving; all 193 unit tests still pass.
- Tooling: integrate knip for dead-code analysis (knip.json + npm script +
CI step). Remove orphaned useLocalStorage.ts; declare the previously
phantom `globals` devDependency.
- Feature: scroll-to-top button on the About page (prefers-reduced-motion
aware, i18n across all four locales).
- Docs: bump to 1.5.0; update CHANGELOG, THIRD-PARTY, ROADMAP (Phase 4 + 5),
CONTRIBUTING.
Co-authored-by: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
Patch release for the toast close-button regression (#52):
- Upgrade sonner v1.7 to v2 — close button now dismisses on click on both desktop and mobile
- Touch hit-area expansion on close button + touch-action: manipulation
- docs/tested-viewports.md documents the manual device test matrix
- README EN + VI link to the new doc
Co-authored-by: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
User report: the toast close button (×) was visible on both desktop and mobile,
but clicking/tapping it didn't dismiss the toast. Reading sonner v1.7.4's
bundled source, the toast root attaches an `onPointerDown` that calls
`r.target.setPointerCapture(r.pointerId)` unconditionally whenever the toast is
dismissible. Combined with React 19's new event delegation (root-attached
listeners instead of document-wide), this pointer capture quirk swallows the
synthetic click event on the close button — so the bundled handler that calls
`dismiss()` never runs. The bug fires on both mouse and touch because the
PointerEvent capture is API-unified.
Upgrade sonner from ^1.7.0 to ^2.0.7. Sonner v2 rewrote the pointer/swipe
handling and ships first-class React 19 support; the close-button click now
fires reliably on both desktop and mobile. The seven `toast.success/warning/
error/info` usage sites and the `<Toaster>` props (`position`, `theme`,
`richColors`, `closeButton`, `toastOptions.classNames`) are API-compatible
between v1 and v2 — typecheck and the 193 unit tests pass without changes.
Bonus: add a `::after` hit-area expansion on `[data-close-button]` (visible
size stays at sonner's 20px default; effective tap target ~36–40px) plus
`touch-action: manipulation` to eliminate the 300ms tap delay on touch
devices. Defensive — sonner v2 already fixes the underlying click issue, but
the larger hit target is a free mobile UX win.
Also adds:
- `docs/tested-viewports.md` — the manual device test matrix the maintainer
has been verifying against (BlackBerry Z30 / Galaxy S9+ / Pixel 3/4/7 /
iPhone SE/12/14 Pro/XR/Pro Max / iPad / BlackBerry PlayBook). Documents the
Nokia Lumia 520 (320x533) as a known limitation below the recommended
minimum 360x640.
- README EN + VI link to the new doc.
- THIRD-PARTY.md bumps sonner version 1.7 to 2.0.7.
Co-authored-by: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
Patch release for the mobile-viewport overlap reported after v1.4.1 (#47):
- Tabs UI for Input/Output on mobile (<md); side-by-side grid stays on md+
- Unread-output dot on the Output tab
- Compact FormatPicker — bottom Sheet on mobile instead of 12 chips inline
- README EN + VI disclose minimum viewport (360×640)
Co-authored-by: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
After v1.4.1 user retested and reported the UI still breaks below ~400x700:
panels overlap below 600h, become nearly invisible below 500h. Root cause is
the grid-rows-2 mobile stack still gives each panel only half the available
height, and when the workspace toolbar wraps 2-3 rows (FormatPicker's 12 chips)
plus header / Home hero / Footer / StatusBar chrome, each row drops below
CodeMirror's minimum rendered content height and the two panels visually overlap.
Tabs UI on mobile (<md)
- Add shadcn Tabs primitive (@radix-ui/react-tabs, MIT)
- ConverterWorkspace renders Tabs on mobile (Input | Output, full-height active
tab) and the side-by-side grid on md+. Both layouts render in parallel so
CodeMirror state survives viewport resize without a remount.
- Output tab shows a 6px dot when output changes while the user is on the Input
tab; the dot clears when they switch over. No auto-switch — user controls.
Compact FormatPicker on mobile
- Mobile: a single "Target format: CSV" button opens a bottom Sheet listing all
12 chips in a 2-3 column grid (reuses the Sheet primitive already shipped
with BatchPanel / SettingsPanel). Saves ~50-80px of toolbar height that
would otherwise be eaten by the chip flex-wrap.
- Desktop: unchanged — 12 chips inline.
Minimum viewport documented
- README EN + VI now state "designed for viewports ≥ 360 × 640; smaller
screens still work but may feel cramped".
THIRD-PARTY.md adds @radix-ui/react-tabs.
Co-authored-by: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
Patch release for the mobile regressions reported on iPhone 14 Pro (#42):
- Header no longer overflows the viewport on phones (brand wordmark hidden below sm)
- Workspace panels stay visible on short and landscape phones (grid-rows-2 mobile split + h-dvh)
- THIRD-PARTY.md catches up with the CodeMirror lang packs (yaml/xml/markdown/sql/legacy-modes)
Co-authored-by: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
Three viewport regressions reported on iPhone 14 Pro (393 portrait, 852x393 landscape) and shorter phones; iPad and tablets were unaffected.
Header overflow
- iPhone 14 Pro is 393px wide; the header's brand wordmark + nav + lang switcher + theme + GitHub icon row summed to ~460px, forcing horizontal page scroll. Hide the "JSONPrism" wordmark below sm (640px) and rely on the BrandMark SVG alone on phones — saves ~90px and the row now fits.
Workspace panels collapsing
- "Output trên một số mẫu điện thoại có chiều dài ngắn không có" + "Khi xoay ngang -> Toàn bộ trường Input và output bị biến mất". Root causes:
1. min-h-[40vh] on each stacked panel (added in 1.4.0 for usable mobile heights) summed to 80vh, which exceeded the available height after the header / Home padding / workspace toolbar / status bar / footer chrome on short phones. The workspace container's overflow-hidden then clipped the lower panel off-screen.
2. h-screen (= 100vh) on the Layout root doesn't account for iOS Safari's dynamic toolbar — the computed height could exceed the actual visible area on rotation.
- Swap min-h-[40vh] for grid-rows-2 (mobile) / md:grid-rows-1 (desktop). Each panel now takes exactly half the workspace height share — always visible, no overflow.
- Swap h-screen for h-dvh (Tailwind v4 dynamic viewport height) so iOS Safari's actual visible area drives the layout.
THIRD-PARTY.md
- Add the five CodeMirror language packs that landed across 1.3.0 + 1.4.0 but weren't listed: lang-yaml, lang-xml, lang-markdown, lang-sql, legacy-modes. All MIT, all @codemirror/*.
Co-authored-by: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
Bumps package.json, src-tauri/Cargo.toml, and src-tauri/tauri.conf.json to 1.4.0 and adds the CHANGELOG entry for the UI/UX polish round (#35, #37):
- Dynamic input/output placeholders in reverse mode
- "Multi-target formats" slogan
- Reverse-mode highlight expanded to Markdown / SQL / TOML / JSONL
- Social links UI: Footer icons + About Community section
- Mobile responsiveness polish
- Mousewheel scroll on input editor no longer requires click-to-focus
- README EN + VI refreshed
Co-authored-by: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
The BlueskyIcon's `<path>` was a single long line exceeding the print
width, which slipped through local lint/build but failed CI's
`format:check`. Wraps the d/transform attributes across lines —
identical output, no SVG change.
Co-authored-by: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
* feat(i18n): dynamic placeholders + Multi-target slogan
- Replace "Eight target formats" with "Multi-target formats" in app.description across en/vi/ja/zh-CN
- Add input_placeholder_format and output_empty_format keys with {{ext}} interpolation
- InputPanel and OutputPanel render extension-aware placeholders in reverse mode (e.g. "Paste your CSV here...", "Output will appear here once you provide valid YAML.")
- Forward mode keeps the original JSON-specific copy
Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
* feat(ui): social links in Footer + About Community section
- Add SocialIcons component with 6 inline-SVG brand icons (Discord, X, Bluesky, Mastodon, Telegram, YouTube), since lucide-react has no brand icons
- Footer now exposes Discord (dev community) / X / Bluesky as a centered icon row, sandwiched between app meta and the maintainer credit
- About page gains a "Community" section between Donate and Third-party, listing all six platforms with icon + label
- Add i18n keys: about.community.* (titled section) and social.* (aria-labels) across en/vi/ja/zh-CN
- Curated based on username.txt: includes dev-relevant + maintainer's public socials; excludes Steam, Discord game server, email, and the Telegram bot (off-topic for the project)
Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
* feat(editor): scroll polish + reverse highlight for md/sql/toml/jsonl
Scroll fix
- .cm-scroller switched from scrollbarWidth: 'none' to 'thin' and explicit overflow: 'auto'. Hiding the native scrollbar was making wheel scroll require a click-to-focus before it engaged on some Chromium builds. Thin themed scrollbar reads fine on both light and dark theme.
Reverse-mode highlight
- Add @codemirror/lang-markdown, @codemirror/lang-sql, @codemirror/legacy-modes
- CodeEditor's EditorLanguage union now covers markdown, sql, and toml
- InputPanel maps jsonl -> json, markdown -> markdown, sql -> sql, toml -> toml; csv/tsv stay plain (no good CodeMirror grammar)
- All extensions go through the existing prismHighlightStyle, so colors stay consistent with forward JSON highlighting
Bundle impact: the three new packs are routed into the existing 'codemirror' manualChunk; no initial-bundle regression.
Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
* feat(ui): mobile responsiveness polish
- Header: nav links Convert/About now always visible (previously hidden md:flex), brand mark + wordmark scale down on small screens, padding tightened to 12px so the 360px viewport fits brand + nav + lang + theme + GitHub icon
- InputPanel/OutputPanel toolbar buttons: icon-only on mobile (label hidden below sm); aria-label and title now carry the text for a11y/tooltips
- ConverterWorkspace panels: min-h-[40vh] on mobile so the stacked Input/Output each keep a usable height instead of collapsing
- Home hero: stack the title and the drop-zone hint on mobile (flex-col), reduce outer padding
- About page: reduce outer padding on mobile (px-4 py-10) to claw back horizontal space
- FormatPicker chips: smaller padding + 11px font on mobile so the 12-format wrap stays compact
Skipped hamburger menu by design — Header only has 2 nav links, the drawer pattern adds bundle and complexity without payoff.
Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
* docs: refresh README EN + VI for Multi-target slogan, full format table, Community section
- Replace "Eight target formats" tagline with "Multi-target formats" (EN) / "Đa định dạng đích" (VI), matching the in-app app.description copy
- VI README format table now mirrors EN: includes BSON / CBOR / MessagePack (Phase 4) and the "Reverse (→ JSON)" column that the VI side was missing
- Bump tech-stack line from Vite 6 to Vite 8 in both files (package.json has been on ^8.0.0 for a while; the About page already reflected this)
- Add a Community section listing Discord (dev community), X, Bluesky, Mastodon, Telegram, and YouTube — same set as the in-app Community section, sourced from the maintainer's public socials
Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
---------
Co-authored-by: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
- Translate the v1.3.3 entry to English to match the rest of CHANGELOG.
- Annotate v1.3.2 as a misdiagnosis: the fix is correct on its own
(the Tauri callback really did miss the extension filter) but it is
not the bug the user reported. The actual user-visible bug was
batch dedup, which v1.3.3 addresses.
- Add a "Verified" section under v1.3.3 listing the manual smoke
environments: Windows Sandbox and Ubuntu 22.04 (Hyper-V VM).
No code changes. Tests / lint / typecheck unaffected.
Co-authored-by: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
`fileFromNativePath` was calling `new File([text], name, { type })`
without `lastModified`. The File API defaults `lastModified` to
`Date.now()` at construction time, so reading the same path twice
produced two File objects with different timestamps — and `batchStore`
dedups on `(name, size, lastModified)`, so dropping the same file
twice through Tauri native drag-drop / native picker added both
copies to the queue with no `duplicate` toast. Web wasn't affected
because `<input type="file">` and `react-dropzone` build File objects
from the OS mtime.
Fix: call `stat()` from `@tauri-apps/plugin-fs` and pass
`mtime.getTime()` into the File constructor. Fall back to an FNV-1a
hash of the path if stat throws (capability missing, file vanished
between read and stat) so repeat drops still dedup.
Also infer `type` from the extension instead of hard-coding
`application/json`. Add `fs:allow-stat` to the default capability.
3 new unit tests for `pathHashAsMillis`. Total: 193.
Co-authored-by: Claude Opus 4.7 (1M context) <noreply@anthropic.com>