Add negative test coverage for memo ID scientific notation and trailing decimal zero

[Copilot]

The Memo.id() validation fix (rejecting non-plain-decimal strings via /^\d+$/) lacked explicit regression tests for the two formats that motivated the fix: scientific notation and trailing decimal zeros — both accepted by BigNumber but fatal to BigInt()/UnsignedHyper.fromString().

Changes

• test/unit/memo_test.js — Added two negative assertions to the existing Memo.id() invalid-argument test block:
  • "1e18" (scientific notation) — silently accepted by BigNumber, crashes UnsignedHyper
  • "1.0" (trailing decimal zero) — same failure path

// trailing decimal zero (BigNumber accepts but must be rejected)
expect(() => StellarBase.Memo.id('1.0')).to.throw(/Expects a uint64/);
// scientific notation (BigNumber accepts but BigInt()/UnsignedHyper crashes)
expect(() => StellarBase.Memo.id('1e18')).to.throw(/Expects a uint64/);

---

📍 Connect Copilot coding agent with Jira, Azure Boards or Linear to delegate work to Copilot in one click without leaving your project management tool.

[github-actions]

Size Change: 0 B

Total Size: 3.53 MB

ℹ️ View Unchanged

Filename	Size
dist/stellar-base.js	2.6 MB
dist/stellar-base.min.js	921 kB

_{compressed-size-action}