Repository navigation
Conversation
Contributor
🔍 Linter ReportClick to expand full reportThis comment was automatically generated by the linter bot. |
Contributor
🔍 Linter ReportClick to expand full reportThis comment was automatically generated by the linter bot. |
Contributor
🔍 Linter ReportClick to expand full reportThis comment was automatically generated by the linter bot. |
shrukul
changed the title
Contributor
🔍 Linter ReportClick to expand full reportThis comment was automatically generated by the linter bot. |
Contributor
🔍 Linter ReportClick to expand full reportThis comment was automatically generated by the linter bot. |
Contributor
🔍 Linter ReportClick to expand full reportThis comment was automatically generated by the linter bot. |
AEAbreu-hub
approved these changes
Apr 28, 2026
AEAbreu-hub
left a comment
AEAbreu-hub
left a comment
Collaborator
There was a problem hiding this comment.
Lots of good content and clean up you've done here. I haven't done a careful edit review yet, but it's passing the lint checks so I won't hold up the content at this stage. Let's get the info out and polish it over time. Thanks for the work here.
added 2 commits
April 30, 2026 02:09
- Use US English spelling (organization) throughout - Remove passedCount from validationSummary — API only returns failed counts - Remove ruleId from validation error responses to avoid exposing internal rule identifiers
Contributor
🔍 Linter ReportClick to expand full reportThis comment was automatically generated by the linter bot. |
- Correct asset request body: nodeId/url → clientItemId and nested asset object with mediaType and value - Correct item response fields: nodeId → clientItemId, validationSummary → summaryText, validationErrors → errorId/errorSummary - Add item-level status values to Core Concepts - Fix pagination documentation: pageSize parameter, scoped to jobs list endpoint only
Contributor
🔍 Linter ReportClick to expand full reportThis comment was automatically generated by the linter bot. |
- Clarify resource hierarchy: items map 1:n to assets (one per image, one per page for multi-page documents) - Replace bb-cortex.adobe.io with abi.adobe.io across docs and OpenAPI spec
Contributor
🔍 Linter ReportClick to expand full reportThis comment was automatically generated by the linter bot. |
added 2 commits
April 30, 2026 03:41
- Add guide covering comment listing, creation, and update (accept, reject, edit) on validation items - Fix Quickstart "What's next" link to point to the new guide - Reorder sidebar: Review Feedback before Using Postman
- Add `assetAttributions` and `corpusAttributions` to Core Concepts and Quickstart response example, including normalised bounding box coordinates - Add pointer to full `BrandValidationError` schema in Review Feedback guide - Add API Reference links on all response examples for omitted fields
Contributor
🔍 Linter ReportClick to expand full reportThis comment was automatically generated by the linter bot. |
Contributor
🔍 Linter ReportClick to expand full reportThis comment was automatically generated by the linter bot. |
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
2 participants
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.
Uh oh!
There was an error while loading. Please reload this page.