Skip to content

fix(browser): preserve nullable decoded text - #22

Closed
ubugeeei wants to merge 1 commit into
mainfrom
codex/fix-browser-null-text
Closed

fix(browser): preserve nullable decoded text#22
ubugeeei wants to merge 1 commit into
mainfrom
codex/fix-browser-null-text

Conversation

@ubugeeei

Copy link
Copy Markdown
Member

Summary

  • return text: null from browser/WASM decode results when core decoded text is absent
  • update browser typings for nullable decoded text
  • keep Vue decode and camera composables displaying text only when present

Closes #4

Validation

  • pnpm install --frozen-lockfile
  • rustfmt --check crates/fastqr_wasm/src/lib.rs
  • cargo check -p fastqr-wasm --target wasm32-unknown-unknown
  • pnpm --filter fastqr task:check
  • pnpm --filter @fastqr/vue task:check

Note: direct tsc -p npm/fastqr_vue/tsconfig.json --noEmit still reports pre-existing strict type errors tracked separately in #18.

@ubugeeei

Copy link
Copy Markdown
Member Author

Landed via #27 after local vp run ci and final GitHub Actions CI passed. Closing this issue-scoped PR to keep the queue and PR list clean.

@ubugeeei ubugeeei closed this May 18, 2026
@ubugeeei
ubugeeei deleted the codex/fix-browser-null-text branch May 18, 2026 04:49
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.

fix(browser): preserve nullable decoded text in wasm results

1 participant