[WIP] Add JSON Structure to TypeScript conversion implementation

[Copilot]

Plan for implementing structuretots: JSON Structure to TypeScript conversion

• Explore and understand the codebase structure
  • Review avrotots.py for TypeScript output patterns and template usage
  • Review structuretocsharp.py for JSON Structure handling patterns
  • Review structuretopython.py for JSON Structure handling patterns
  • Examine template directories and test patterns
  • Check commands.json format for CLI integration
• Create structuretots.py module
  • Implement StructureToTypeScript class with all JSON Structure type mappings
  • Support all JSON Structure Core types (primitives, extended types, compound types)
  • Handle namespaces, definitions, and type references
  • Support $extends and $offers/$uses (add-ins) - basic implementation
  • Support abstract types - basic implementation
  • Support required/optional properties
  • Support type annotations (maxLength, precision, scale, etc.) - delegated to TypeScript
• Create Jinja templates for TypeScript generation
  • class_core.ts.jinja for object types
  • enum_core.ts.jinja for enums
  • Project configuration templates (tsconfig, package.json, gitignore)
• Add CLI command integration
  • Register s2ts command in commands.json
• Create comprehensive tests
  • Test basic types conversion
  • Test complex types (choice, tuple)
  • Test extended types (decimal, date, uuid, etc.)
  • Test collections (array, set, map)
  • Test inheritance and extensions
  • Test abstract types
  • Test validation constraints
• Lint, build and validate changes
  • All tests passing
  • CLI command verified
  • Generated code manually inspected
• Run code review and security scan

Original prompt

---

This section details on the original issue you should resolve

<issue_title>Add structuretots: JSON Structure to TypeScript conversion</issue_title>
<issue_description>## Overview
Implement conversion from JSON Structure schemas to TypeScript types.

Requirements

This conversion should:

1. Lean on the corresponding Avro conversion (avrotots) as precedent for output structure, including use of Jinja templates where applicable
2. Cover the full breadth of the JSON Structure Core spec as defined in draft-vasters-json-structure-core-00
3. Follow the patterns established by structuretocsharp and structuretopython, including their continued support for Avro schemas

Implementation Guidance

• Review avrotize/avrotots.py for output patterns and template usage
• Review avrotize/structuretocsharp.py and avrotize/structuretopython.py for the JSON Structure handling patterns
• Ensure all JSON Structure Core types are supported:
  • JSON Primitive Types: string, number, boolean, null
  • Extended Primitive Types: binary, int8-128, uint8-128, float8/float/double, decimal, date, datetime, time, duration, uuid, uri, jsonpointer
  • Compound Types: object, array, set, map, tuple, any, choice (both tagged and inline unions)
• Support JSON Structure-specific features:
  • Namespaces and definitions
  • Type references ($ref)
  • Extensions ($extends) and add-ins ($offers/$uses)
  • Abstract types
  • Required/optional properties
  • Type annotations (maxLength, precision, scale, contentEncoding, etc.)

References

• JSON Structure Core Spec: https://www.ietf.org/archive/id/draft-vasters-json-structure-core-00.txt
• Avro precedent: avrotize/avrotots.py
• JSON Structure precedents: avrotize/structuretocsharp.py, avrotize/structuretopython.py
  </issue_description>

Comments on the Issue (you are @copilot in this section)

• Fixes Add structuretots: JSON Structure to TypeScript conversion #51

---

✨ Let Copilot coding agent set things up for you — coding agent works faster and does higher quality work when set up for your repo.

[clemensv]

@copilot

Additional Requirements

Documentation

The README.md file needs to be updated to include documentation for this new conversion feature, following the pattern established for existing conversions.

Testing

All tests must follow the established testing patterns:

• For programming language outputs (C#, Java, Python, TypeScript, JavaScript, C++, Go, Rust): Tests must run the embedded tests in the code outputs to verify correctness
• For schema language outputs (CSV, Protobuf, XSD, GraphQL, etc.): Tests must compare the generated output to a desired output reference (-ref) schema stored in the /test/struct directory

This follows the pattern established for the Avro conversion tests in the repository.

[clemensv]

Closing duplicate PR for TypeScript conversion. Keeping the newer PR #97 for this issue.