Open KROSF opened 1 week ago
Current TypeScript typings do not completely align with the specifications provided in the API documentation.
For instance, in the StatusResponse type:
Ensure the typings accurately reflect all documented properties, why all of them are marked as optional?
Unless otherwise specified as required in Apple documentation, indicated by the (required) tag, all fields are implicitly optional.
Current TypeScript typings do not completely align with the specifications provided in the API documentation.
For instance, in the StatusResponse type:
Ensure the typings accurately reflect all documented properties, why all of them are marked as optional?