docs(pricing): add cu:auto markers to Compute Unit Costs tables#1424
Draft
SahilAujla wants to merge 1 commit into
Draft
docs(pricing): add cu:auto markers to Compute Unit Costs tables#1424SahilAujla wants to merge 1 commit into
SahilAujla wants to merge 1 commit into
Conversation
Wraps each generated CU table in {/* cu:auto product="<tag>" */} ...
{/* cu:auto end */} markers so the new
UpdateComputeUnitCostsFromDaikonWorkflow (dashboard repo, DX-3112) can
regenerate table rows from Daikon topconfig daily while leaving all
hand-written prose, headers, and footnotes untouched. Markers are MDX
comments and do not render.
Bandwidth-priced and rules sections (Yellowstone gRPC, WebSocket
Subscriptions, Webhooks, error codes) intentionally have no markers and
stay fully manual.
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
🔗 Preview Mode
|
5 tasks
Collaborator
Author
|
@codex review |
|
Codex Review: Didn't find any major issues. Already looking forward to the next diff. Reviewed commit: ℹ️ About Codex in GitHubYour team has set up Codex to review pull requests in this repo. Reviews are triggered when you
If Codex has suggestions, it will comment; otherwise it will react with 👍. Codex can also answer questions or update the PR. Try commenting "@codex address that feedback". |
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.
Description
One-time setup for automating the Compute Unit Costs pricing page from Daikon topconfig (DX-3112). Dynamic CU pricing means customers are billed updated prices immediately after a chain-config update, so this hand-maintained page needs to regenerate automatically.
This PR wraps each generated CU table in
{/* cu:auto product="<tag>" */}…{/* cu:auto end */}markers — MDX comments that do not render. The newUpdateComputeUnitCostsFromDaikonWorkflowin the dashboard repo (companion PR: OMGWINNING/dashboard#8087) rewrites only the table rows between markers on a daily cron; all prose, headers, and footnotes outside markers stay hand-written and are never touched. Theproducttag is the stable key the automation matches on — not the header text — so renaming a header or moving a whole block (markers included) is safe.Summary
cu:automarkers (marker insertion only — zero changes to table content in this PR)eth_sendUserOperation,alchemy_requestFeePayerwithprefundRent) live outside markers and persist across regenerationsTest Plan
prettier --checkpasses on the pageLINEAR TASK: https://linear.app/alchemyapi/issue/DX-3112/automate-the-compute-unit-costs-pricing-page-from-daikon-topconfig