Fix Interval schema to reflect ISO 8601 string serialization#463
Open
benedikt-buchert wants to merge 1 commit intoAdobeDocs:mainfrom
Open
Fix Interval schema to reflect ISO 8601 string serialization#463benedikt-buchert wants to merge 1 commit intoAdobeDocs:mainfrom
benedikt-buchert wants to merge 1 commit intoAdobeDocs:mainfrom
Conversation
The Adobe Target API serializes Interval values as ISO 8601 interval strings (e.g. "2023-11-01T15:00Z/2024-06-27T10:00Z") rather than JSON objects. Update the schema to use oneOf so both the string form returned by the API and the object form are valid. Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
The Adobe Target API serializes
Intervalvalues as ISO 8601 interval strings (e.g.2023-11-01T15:00Z/2024-06-27T10:00Z) rather than JSON objects. The current schema definesIntervalastype: object, which causes validation errors in strictly-typed clients.Observed API response:
```json
{ "reportInterval": "2023-11-01T15:00Z/2024-06-27T10:00Z" }
```
Current schema (incorrect):
```json
{ "type": "object", "properties": { "start": ..., "end": ..., ... } }
```
Fix: Change
IntervaltooneOf: [string, object]so both the ISO 8601 string form returned by the API and the structured object form are considered valid.🤖 Generated with Claude Code