Fix parseStructTag to reject malformed inputs

[Danny-Devs]

Description

parseStructTag silently accepted inputs with empty components (e.g. ::foo::Bar, where the empty address normalized to 0x0) and inputs with trailing content after type parameters (e.g. Coin<u8>GARBAGE). Both cases produced structurally incorrect StructTag objects without raising an error.

This adds two validation guards:

1. Empty component rejection: After splitting on ::, validate that address and module are non-empty strings. Previously, ::foo::Bar would silently have its empty address padded to 0x0 by normalizeSuiAddress("").

2. Trailing content rejection: After extracting name, validate that if type parameters exist (<...>), the string ends with >. Previously, Coin<u8>GARBAGE would silently drop the trailing content.

Both throw Error('Invalid struct tag: ${type}'), consistent with the existing error for inputs with fewer than 3 :: segments.

Test plan

Added 6 test cases to test/unit/types/common.test.ts:

Empty component rejection:

• ::foo::Bar — empty address
• 0x2::::Bar — empty module
• 0x2::foo:: — empty name

Trailing content rejection:

• 0x2::coin::Coin<u8>GARBAGE — trailing characters
• 0x2::foo::Bar<bool> — trailing space
• 0x2::foo::Bar<u64>xyz — trailing alphanumeric

All 290 unit tests pass. Full e2e suite (722 tests) verified against local Sui network via Testcontainers — zero regressions.

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated (UTC)
sui-typescript-docs	Ready	Preview, Comment	Feb 26, 2026 5:23am