traces

[aigerimu]

closes #302

[github-actions]

To fix the formatting issues:

1. Install necessary dependencies: npm ci
2. Then, run this command:

npx remark -o --silent --silently-ignore ecosystem/rpc/traces.mdx 

[github-actions]

Thanks for the update to the traces docs under ecosystem/rpc. There’s one high‑severity link issue that needs a small fix before merge.

Findings (1)

High (1)

[HIGH] Broken internal link to non-existent API reference

Location:

mintlify-ton-docs/ecosystem/rpc/traces.mdx

Lines 39 to 40 in 22b1862

	To fetch transaction data, use the high-level [`GET /traces`](/api-reference/actions/get-traces) endpoint.
	This method allows you to retrieve all related transactions for a given operation, without parsing individual transactions.

Description:
The page links “GET /traces” to /api-reference/actions/get-traces, which does not exist in this repository, resulting in a dead internal anchor. Broken internal links are prohibited by the style guide and are treated as high severity (see https://github.com/tact-lang/mintlify-ton-docs/blob/main/contribute/style-guide-extended.mdx?plain=1#L528-L528 and https://github.com/tact-lang/mintlify-ton-docs/blob/main/contribute/style-guide-extended.mdx?plain=1#L31-L31). The correct traces endpoint defined in‑repo is GET /api/v3/traces (see ecosystem/rpc/ton-center-http-api-v-3.yaml?plain=1#L1511-L1511).

Suggestion:

- To fetch transaction data, use the high-level [`GET /traces`](/api-reference/actions/get-traces) endpoint.
+ To fetch transaction data, use the high-level `GET /traces` endpoint.

- To fetch transaction data, use the high-level [`GET /traces`](/api-reference/actions/get-traces) endpoint.
+ To fetch transaction data, use the high-level `GET /api/v3/traces` endpoint.

- To fetch transaction data, use the high-level [`GET /traces`](/api-reference/actions/get-traces) endpoint.
+ To fetch transaction data, use the high-level Get Traces endpoint in [TON Center API v3](/ecosystem/rpc/ton-center-http-api-v-3).

[github-actions]

To fix the formatting issues:

1. Install necessary dependencies: npm ci
2. Then, run this command:

npx remark -o --silent --silently-ignore ecosystem/rpc/traces.mdx 

[github-actions]

To fix the formatting issues:

1. Install necessary dependencies: npm ci
2. Then, run this command:

npx remark -o --silent --silently-ignore ecosystem/rpc/traces.mdx 

[verytactical]

• Wasn't this article meant to go into Ecosystem > Explorers?
• Probably m4' and m4'' were meant to be m4 and m4', otherwise it's not consistent with the rest of them
• After internal discussion it turned out we're not satisfied with how the image looks after all :) The spacing is off, and it doesn't really look professional. Could you please create an issue, so that we can ask designers to make a better one in the future?

[aigerimu]

• Wasn't this article meant to go into Ecosystem > Explorers?

This is another article from this issue

• Probably m4' and m4'' were meant to be m4 and m4', otherwise it's not consistent with the rest of them

Will fix it. Thank you

[github-actions]

To fix the formatting issues:

1. Install necessary dependencies: npm ci
2. Then, run this command:

npx remark -o --silent --silently-ignore ecosystem/rpc/traces.mdx 

[github-actions]

To fix the formatting issues:

1. Install necessary dependencies: npm ci
2. Then, run this command:

npx remark -o --silent --silently-ignore ecosystem/rpc/traces.mdx