Description
The SDK's response models do not include an errors field. When the LinkedIn API returns a partial success (some records created, some failed), the error details for individual failures are dropped because the response model has no field to hold them.
Impact
Users cannot programmatically handle partial failures in batch operations. The API returns errors (field-level validation failures, permission errors, etc.) but they're silently discarded during response deserialization.
Expected behavior
Response models should include an optional errors field that preserves the API's error details for individual records.
Additional context
Related: client_secret is currently required in the auth flow, but it should be optional for public clients (native apps, SPAs) that use PKCE. See PR #75 for a fix addressing both issues.
Description
The SDK's response models do not include an
errorsfield. When the LinkedIn API returns a partial success (some records created, some failed), the error details for individual failures are dropped because the response model has no field to hold them.Impact
Users cannot programmatically handle partial failures in batch operations. The API returns errors (field-level validation failures, permission errors, etc.) but they're silently discarded during response deserialization.
Expected behavior
Response models should include an optional
errorsfield that preserves the API's error details for individual records.Additional context
Related:
client_secretis currently required in the auth flow, but it should be optional for public clients (native apps, SPAs) that use PKCE. See PR #75 for a fix addressing both issues.