[INJIVER-1512] update readme

[srikanth716]

Summary by CodeRabbit

• Breaking Changes
  • Documentation added for v0.8.0 detailing API contract changes and deprecated call patterns.
• Documentation
  • README updated with migration guidance and examples to adopt the new API shapes.
  • Expanded features section covering additional encoding/decoding capabilities (CBOR, base45, etc.) and related usage scenarios.

_{✏️ Tip: You can customize this high-level summary in your review settings.}

[coderabbitai]

Walkthrough

Added a "Breaking Changes" section to js/Readme.md documenting version 0.8.0 API signature changes for getMappedData and decodeMappedData, deprecation notices for old signatures, and migration guidance plus expanded encoding/decoding feature notes.

Changes

Cohort / File(s)	Summary
Documentation js/Readme.md	Inserted "Breaking Changes" for v0.8.0: getMappedData signature changed to getMappedData(jsonData, keyMapper, valueMapper, cborEnable?); decodeMappedData changed to decodeMappedData(data, keyMapper, valueMapper?); deprecation notices and migration examples; expanded encoding/decoding features (CBOR, base45, etc.).

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~3 minutes

Suggested reviewers

• ckm007

Poem

🐰 Hopped into README, tidy and bright,
New signatures sketched in the moonlight,
Deprecated trails gently laid to rest,
Migration steps help users be their best,
A rabbit's cheer for docs done right.

🚥 Pre-merge checks | ✅ 2 | ❌ 1

❌ Failed checks (1 inconclusive)

Check name	Status	Explanation	Resolution
Title check	❓ Inconclusive	The title 'update readme' is vague and doesn't specify which readme or what changes were made. While it references the actual change (updating js/Readme.md), it lacks specificity about the breaking changes and API signature modifications documented.	Revise the title to be more specific, such as 'Document breaking changes in getMappedData and decodeMappedData signatures for v0.8.0' to clearly convey the primary change.

✅ Passed checks (2 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

---

📜 Recent review details

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 4299f1e and a12c93e.

📒 Files selected for processing (1)

• js/Readme.md

✅ Files skipped from review due to trivial changes (1)

• js/Readme.md

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[coderabbitai]

Actionable comments posted: 1

🤖 Fix all issues with AI agents

In @js/Readme.md:
- Around line 15-42: The docs use inconsistent parameter names in the
breaking-changes summary: change the `valueMapperFunction?` mention for
`decodeMappedData` to `valueMapper?` so it matches the rest of the documentation
and the `getMappedData(jsonData, keyMapper, valueMapper, cborEnable?)`
signature; update the summary text where `decodeMappedData(data, keyMapper,
valueMapperFunction?)` appears to `decodeMappedData(data, keyMapper,
valueMapper?)`, ensuring both `getMappedData` and `decodeMappedData` use
`valueMapper` consistently.

📜 Review details

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between c169030 and 4299f1e.

📒 Files selected for processing (1)

• js/Readme.md

🔇 Additional comments (1)

js/Readme.md (1)

15-42: Excellent breaking changes documentation with clear migration path.

The new "Breaking Changes" section is well-structured and provides clear API contract updates. The detailed documentation sections for both getMappedData() and decodeMappedData() include comprehensive parameter descriptions, practical examples, and proper deprecation/breaking change notices. The migration guide (lines 237–255) effectively walks users through the changes with before/after code examples and a clear "Key differences" section.

Also applies to: 143-235