[docs-agent] Remove reportSpam V3 endpoint from NFT API docs - #1554
Open
alchemy-bot wants to merge 1 commit into
Open
[docs-agent] Remove reportSpam V3 endpoint from NFT API docs#1554alchemy-bot wants to merge 1 commit into
alchemy-bot wants to merge 1 commit into
Conversation
Removes all documentation references to the `reportSpam` NFT V3 endpoint (previously rendered at /docs/reference/nft-api-endpoints/nft-api-endpoints/nft-spam-endpoints/report-spam-v-3).
* src/openapi/nft/nft.yaml: delete the /v3/{apiKey}/reportSpam operation block (operationId reportSpam-v3).
* content/api-reference/data/nft-api/nft-api-endpoints.mdx: drop the reportSpam row from the NFT Spam Endpoints table.
* content/api-reference/pricing-resources/pricing/compute-unit-costs.mdx: drop the reportSpam CU row inside the cu:auto product="nft" block. Companion chain-config PR removes the endpoint from Daikon's topconfig so the daily regeneration doesn't restore this row.
* content/redirects.yml: repoint the existing V2 report-spam redirect at the NFT endpoints overview (was pointing at the now-removed V3 page); add a new redirect for the V3 URL itself. Follows the DOCS-196 pattern.
Refs DOCS-201
Requested-by: @oskarciupider-alchemy
🔗 Preview Mode
|
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
Removes all documentation references to the
reportSpamNFT V3 endpoint (previously rendered at /docs/reference/…/report-spam-v-3) so the page 404s and callers redirect to the NFT endpoints overview.Companion chain-config PR removes
reportSpamfrom Daikon'stopconfig.ymlso the daily generator doesn't restore the CU row here.Changes
src/openapi/nft/nft.yaml— delete the/v3/{apiKey}/reportSpamoperation block (operationIdreportSpam-v3).content/api-reference/data/nft-api/nft-api-endpoints.mdx— drop thereportSpamrow from the NFT Spam Endpoints table.content/api-reference/pricing-resources/pricing/compute-unit-costs.mdx— drop thereportSpam | 0 | 10row inside the{/* cu:auto product="nft" */}block.content/redirects.yml— repoint the existing V2report-spamredirect at the NFT endpoints overview (was pointing at the now-removed V3 page); add a new redirect for the V3report-spam-v-3URL itself. Follows the DOCS-196 pattern.Linear
DOCS-201 — Remove reportSpam V3 endpoint from docs + Daikon config
Notes
reportSpamContract(the other endpoint in Daikon'sreport_spammethod group) is already flagged in-source as#NftApiV3DeprecatedEndpointsand has zero docs presence — leaving it in place. If the CU generator surfaces areportSpamContractrow after the chain-config PR merges, follow-up needed.Requested by
@oskarciupider-alchemy (via Slack thread)