Update using-jinja.md

[aruness]

Updated the get_payment_methods macro call

What are you changing in this pull request and why?

Checklist

• Review the Content style guide so my content adheres to these guidelines.
• For docs versioning, review how to version a whole page and version a block of content.
• Add a checklist item for anything that needs to happen before this PR is merged, such as "needs technical review" or "change base branch."

Adding or removing pages (delete if not applicable):

• Add/remove page in website/sidebars.js
• Provide a unique filename for new pages
• Add an entry for deleted pages in website/static/_redirects
• Run link testing locally with npm run build to update the links that point to deleted pages

[welcome]

Hello!👋 Thanks for contributing to the dbt product documentation and opening this pull request! ✨
We use Markdown and some HTML to write the dbt product documentation. When writing content, you can use our style guide and content types to understand our writing standards and how we organize information in the dbt product docs.
We'll review your contribution and respond as soon as we can. 😄

[vercel]

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name	Status	Preview	Comments	Updated (UTC)
docs-getdbt-com	✅ Ready (Inspect)	Visit Preview	💬 Add feedback	Feb 1, 2024 8:14am

[mirnawong1]

hey @aruness , thanks for opening this pr up and great first contribution! i'd love to understand more on why you think we should add (column_name, relation) %} to the macro? from my understanding, the {% macro get_payment_methods() %} example is correct since it's meant to fetch payment methods from a particular relation using the get_column_values macro.

would love to hear your thoughts on this!

[aruness]

Oh, I get it, closing this PR. I apologize for my oversight.

…

________________________________ From: mirnawong1 ***@***.***> Sent: Thursday, February 1, 2024 5:24 PM To: dbt-labs/docs.getdbt.com ***@***.***> Cc: Arun Mohanty ***@***.***>; Mention ***@***.***> Subject: Re: [dbt-labs/docs.getdbt.com] Update using-jinja.md (PR #4843) hey @aruness<https://github.com/aruness> , thanks for opening this pr up and great first contribution! i'd love to understand more on why you think we should add (column_name, relation) %} to the macro? from my understanding, the {% macro get_payment_methods() %} example is correct since it's meant to fetch payment methods from a particular relation using the get_column_values macro. would love to hear your thoughts on this! — Reply to this email directly, view it on GitHub<#4843 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/A2EVLTINOD2JQ7HFMPF6UUDYRN66TAVCNFSM6AAAAABCUNTD76VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTSMRRGE2TMMJVGQ>. You are receiving this because you were mentioned.Message ID: ***@***.***>

[aruness]

Closed, seems like an oversight from my end.

[mirnawong1]

no worries! thanks for opening this pr up and let us know if you have any questions!