[chore] Add anchors to individual attributes in a markdown table #1041

[RichardChukwu]

Fixes #1041

Changes

• Added anchor tags to individual attributes in the markdown table.

• Each attribute now has a corresponding element, allowing direct linking to the specific attribute from the table of contents or other parts of the documentation.

• The anchor is dynamically generated using the attribute’s name, converted to a URL-friendly format (lowercase, spaces replaced with hyphens).

• This ensures that each attribute can be easily referenced by creating links to the anchor IDs.

Merge requirement checklist

• CONTRIBUTING.md guidelines followed.
• Change log entry added, according to the guidelines in When to add a changelog entry.
  • If your PR does not need a change log, start the PR title with [chore]
• schema-next.yaml updated with changes to existing conventions.

[joaopgrassi]

Ah.. I forgot that the link check may not work/like the anchor links in the URL 😞. Hum not sure if there's a way around it. I will try to check.

Edit: tcort/markdown-link-check#331

[RichardChukwu]

Ooh, alright

[joaopgrassi]

I pushed a workaround that skips local anchor links for now. Let's see if it passes.

[RichardChukwu]

Hey @joaopgrassi I guess the test passed?

Thanks for the workaround. What next now?

[joaopgrassi]

Needs more approvals, so we need to wait for others to review it as well.

[trisch-me]

thanks! lgtm

[lmolkova]

Thanks for doing this!

It would also be great to update the markdown tables that already reference registry attributes.

E.g. here

semantic-conventions/docs/http/http-spans.md

Line 145 in e038c11

| [`http.request.method`](/docs/attributes-registry/http.md) | string | HTTP request method. [1] | `GET`; `POST`; `HEAD` | `Required` |  |

[RichardChukwu]

@lmolkova Sure, but I suggest that can be addressed in a different PR as a different issue after this is merged, for clarity sake.

Your thoughts?

[lmolkova]

@RichardChukwu sure!