Skip to content

fix: Use string IDs instead of numbers for Fixle API compatibility#5

Open
apotema wants to merge 1 commit intomainfrom
fix/uuid-string-ids
Open

fix: Use string IDs instead of numbers for Fixle API compatibility#5
apotema wants to merge 1 commit intomainfrom
fix/uuid-string-ids

Conversation

@apotema
Copy link
Collaborator

@apotema apotema commented Feb 3, 2026

Summary

  • Fixle Rails uses UUIDs (strings) for all resource IDs, not integers
  • Updated SDK to use string types for IDs
  • Removed parseInt() calls that would return NaN on UUID strings
  • Added documentId and fileUrl fields to triggerApplianceReport response

Changes

  • findOrCreateProperty() now returns Promise<string> instead of Promise<number>
  • createInspection() now takes propertyId: string and returns Promise<string>
  • createAppliance() now takes propertyId: string and inspectionId?: string
  • triggerApplianceReport() now takes inspectionId: string and returns additional fields

Test plan

  • Verify SDK compiles
  • Integration test with Fixle staging

🤖 Generated with Claude Code

@apotema @claude
fix: Use string IDs instead of numbers for Fixle API compatibility
8326ab2 
Fixle Rails uses UUIDs (strings) for all resource IDs, not integers.
This change updates the SDK to:

- Change return types from number to string for findOrCreateProperty,
  createInspection
- Change parameter types from number to string for all methods
- Remove parseInt() calls that would fail on UUID strings
- Add documentId and fileUrl to triggerApplianceReport response

Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

No reviews

Assignees

No one assigned

Labels

None yet

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

1 participant

@apotema

Comments