Skip to content

Escape the brackets in the text link #6726

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Jul 14, 2025
Merged

Escape the brackets in the text link #6726

merged 1 commit into from
Jul 14, 2025

Conversation

letzya
Copy link
Collaborator

@letzya letzya commented Jul 14, 2025

User description

Contributor checklist

  • Reviewed PR Code suggestions and updated accordingly
  • Tyklings: Labled the PR with the relevant releases
  • Tyklings: Added Jira DX PR ticket to the subject

New Contributors



PR Type

Documentation


Description

  • Escaped curly brackets in Markdown link text for clarity

  • Improved documentation formatting for parameter references

  • No functional or code logic changes

  • Enhances readability in developer documentation


Changes diagram

flowchart LR
  A["Documentation with unescaped brackets"] -- "Escape brackets" --> B["Documentation with escaped brackets"]
Loading

Changes walkthrough 📝

Relevant files
Documentation
inclusive-naming-policy.md
Escape curly brackets in Markdown link text                           

tyk-docs/content/developer-support/inclusive-naming-policy.md

  • Escaped curly brackets in Markdown link text for parameter references
  • Improved clarity and formatting in documentation
  • +2/-2     

    Need help?
  • Type /help how to ... in the comments thread for any questions about PR-Agent usage.
  • Check out the documentation for more information.
  • Copy link
    Contributor

    ⚠️ Deploy preview for PR #6726 did not become live after 3 attempts.
    Please check Netlify or try manually: Preview URL

    Copy link
    Contributor

    PR Reviewer Guide 🔍

    Here are some key observations to aid the review process:

    ⏱️ Estimated effort to review: 1 🔵⚪⚪⚪⚪
    🧪 No relevant tests
    🔒 No security concerns identified
    ⚡ No major issues detected

    Copy link
    Contributor

    PR Code Suggestions ✨

    No code suggestions found for the PR.

    Copy link
    Contributor

    PR Analysis: Escaping Curly Brackets in Markdown Link Text

    This PR makes a small but important documentation improvement by escaping curly brackets in Markdown link text for parameter references in the inclusive-naming-policy.md file.

    Changes Made

    The PR modifies two lines in the file by adding backslash escapes (\) before curly brackets in Markdown link text:

    Before:

    - [version_data.versions.{version-name}.extended_paths.black_list]({{< ref "api-management/traffic-transformation/block-list#api-definition" >}})
    - [version_data.versions.{version-name}.extended_paths.white_list]({{< ref "api-management/traffic-transformation/allow-list#api-definition" >}})

    After:

    - [version_data.versions.\{version-name\}.extended_paths.black_list]({{< ref "api-management/traffic-transformation/block-list#api-definition" >}})
    - [version_data.versions.\{version-name\}.extended_paths.white_list]({{< ref "api-management/traffic-transformation/allow-list#api-definition" >}})

    Impact and Benefits

    1. Improved Readability: Escaping the curly brackets makes it clearer that these are literal characters in parameter names rather than Markdown or template syntax.

    2. Prevents Rendering Issues: Unescaped curly brackets in Markdown can sometimes be misinterpreted by rendering engines, potentially causing display problems.

    3. Better Documentation Practices: This change follows best practices for technical documentation by properly escaping special characters.

    This is a straightforward documentation improvement with no functional changes to code or logic. The change enhances the clarity of parameter references in the inclusive naming policy documentation.


    Tip: Mention me again using /probe <request>.
    Powered by Probe AI

    Copy link

    netlify bot commented Jul 14, 2025

    PS. Add to the end of url /docs/nightly

    Name Link
    🔨 Latest commit 1bc0aa3
    🔍 Latest deploy log https://app.netlify.com/projects/tyk-docs/deploys/687542e4cfe6f30008e942e8
    😎 Deploy Preview https://deploy-preview-6726--tyk-docs.netlify.app
    📱 Preview on mobile
    Toggle QR Code...

    QR Code

    Use your smartphone camera to open QR code link.

    To edit notification comments on pull requests, go to your Netlify project configuration.

    @letzya letzya merged commit d9ecd18 into master Jul 14, 2025
    15 checks passed
    @letzya letzya deleted the letz-fix-url-text2 branch July 14, 2025 18:03
    @sharadregoti
    Copy link
    Contributor

    /release to release-5.8

    @letzya
    Copy link
    Collaborator Author

    letzya commented Jul 14, 2025

    fixing so mintlify won't break @yurisasuke

    Copy link
    Contributor

    tykbot bot commented Jul 14, 2025

    Working on it! Note that it can take a few minutes.

    tykbot bot pushed a commit that referenced this pull request Jul 14, 2025
    Escape the brackes in the text link
    
    (cherry picked from commit d9ecd18)
    Copy link
    Contributor

    tykbot bot commented Jul 14, 2025

    @sharadregoti Created merge PRs

    buger added a commit that referenced this pull request Jul 14, 2025
    Escape the brackets in the text link (#6726)
    
    Escape the brackes in the text link
    Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
    Projects
    None yet
    Development

    Successfully merging this pull request may close these issues.

    2 participants