Conversation
docs: document merge-method rule and broken-link caveat in CLAUDE.md
#193) * docs(restapi): document NoTransactionToCancel error and release REST API 2.29.0 Adds error code 1005 (NoTransactionToCancel) to the /transactions response table, distinguishing "no transaction to cancel" from the generic CancelOperationNotAllowed (1003) case, and cuts the 2.29.0 docs version to publish it. * Corrected no reader reversal responses updated responses for reversals without reader --------- Co-authored-by: ecunado <ecunado@ecunados-MacBook-Pro.local> Co-authored-by: AlexDLL31 <alexdll@protonmail.com>
…ject (#194) * docs(restapi): fix Reversal response docs and add ViscusReversalResponse object The Reversal endpoint's Returns table linked to DeferredTokenizationResponse (copy-paste from the Deferred Tokenization section, added by cloudapi PR #432). No ViscusReversalResponse object existed to link to, so it is now documented with the real gateway field set. Also fixes the restobjects.md link that pointed to the non-existent restendpoints#reversal-operations anchor, and adds the missing timestamp parameter to the endpoint's Parameters table. * docs(restapi): drop internal Viscus prefix from Reversal object names Sibling objects (BatchCloseRequest, MotoReversalRequest, etc.) don't carry implementation-detail prefixes; ViscusReversalRequest/ViscusReversalResponse leaked the internal cloudapi model class name into public docs. --------- Co-authored-by: ecunado <ecunado@ecunados-MacBook-Pro.local>
changes/fixes that were sitting on next and apply to 2.29.0 were added to the restendpoints and objects pages
* updated 2.29.0 with Next changes/fixes that were sitting on next and apply to 2.29.0 were added to the restendpoints and objects pages * docs: fix Reversal/Sale/Refund docs, correct release-notes attribution, and repair dead anchors REST API (2.28.0 & 2.29.0): - Reversal (no-reader) endpoint: add info note clarifying that reversals through this endpoint are attributed to the original device in Analytics and won't appear in the Handpoint Payments App. - Sale and Refund (MOTO) endpoints: add 200 OK example response tabs. - MOTO Reversal: remove the incorrect "Optional merchant references: customerReference, transactionReference" line - MotoReversalRequest does not support these fields. - Release notes: move the "Reversal without reader" feature entry to a new 2.28.0 section, since that's the version it actually shipped in, and note that batchNumber is now optional on POST /close in 2.29.0. Windows SDK (all versions, 3.2.0 through current): - Fix #status-info anchor to match the real statusInfo heading ID (kept the legacy kebab-case form in 3.2.0, the one version whose heading has no explicit anchor and still relies on the auto-slug). - Fix OperationStartResul typo (missing trailing "t") to OperationStartResult in windowstransactions.md. - Remove two dead self-page anchor links (#7 on ConnectionStatusChanged, #11 on TransactionResultReady) that pointed to nonexistent legacy numbered anchors; kept the surrounding text, just de-linked it. Android SDK (all versions with the section): - Add the missing {#cloudTokenizedPaymentsOperations} anchor to the "Cloud Tokenized Payments Operations" heading, fixing a broken cross-plugin anchor referenced from the Windows, JavaScript, and REST API docs. yarn build passes with no new broken links/anchors introduced. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com> --------- Co-authored-by: Claude Sonnet 5 <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
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.
No description provided.