Skip to content

fix: array elements starting with number followed by text parsed as string#57

Merged
shreyasbhat0 merged 2 commits intomainfrom
fix/issue-56-array-number-string-parsing
Mar 4, 2026
Merged

fix: array elements starting with number followed by text parsed as string#57
shreyasbhat0 merged 2 commits intomainfrom
fix/issue-56-array-number-string-parsing

Conversation

@shreyasbhat0
Copy link
Copy Markdown
Member

Summary

  • Fixes inline array parsing where values like 1.0 something were truncated to just the number (Number(1)) instead of being parsed as String("1 something")
  • parse_tabular_field_value() now checks for trailing string tokens after Number/Integer tokens and treats the combined value as a string, matching the behavior of regular field value parsing

Test plan

  • Added test test_array_element_number_followed_by_string covering number+text and pure number cases
  • All 151 tests passing

Fixes #56

…as string

When parsing inline array values, numbers followed by string tokens
(e.g., `1.0 something`) were incorrectly truncated to just the number.
The fix checks for trailing string tokens after Number/Integer tokens
in parse_tabular_field_value() and treats the combined value as a string,
matching the behavior of regular field value parsing.

Fixes #56
@shreyasbhat0 shreyasbhat0 requested a review from a team as a code owner March 4, 2026 14:55
@shreyasbhat0 shreyasbhat0 merged commit 07c6640 into main Mar 4, 2026
@shreyasbhat0 shreyasbhat0 deleted the fix/issue-56-array-number-string-parsing branch March 4, 2026 14:57
@github-actions github-actions bot mentioned this pull request Mar 4, 2026
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.

Array elements starting with a number are incorrectly truncated and parsed as Number

1 participant