fix: term_link filter

[jasonbahl]

Description

This fixes the term_link filter callback to not modify the term link urls for GraphQL requests.

Related Issue(s):

fixes: #1613

Testing

BEFORE:

Term uri is absolute in the GraphQL Response

AFTER:

The term uri is relative in the GraphQL response

But in the admin UIs the term links are absolute with the alternate Faust front-end domain.

[changeset-bot]

⚠️ No Changeset found

Latest commit: 6929187

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

[github-actions]

📦 Next.js Bundle Analysis for @faustwp/getting-started-example

This analysis was generated by the Next.js Bundle Analysis action. 🤖

This PR introduced no changes to the JavaScript bundle! 🙌

[mindctrl]

These tests are failing, and it seems to be due to the # in the branch name, which translates to a URL that isn't working well with npx create-next-app.

Clicking that link gives me a 404: https://github.com/wpengine/faustjs/tree/fix/#1613-term_link_callback

The encoded version works: https://github.com/wpengine/faustjs/tree/fix/%231613-term_link_callback

[jasonbahl]

@mindctrl do you want me to rename my branch and open a new PR?

[mindctrl]

@jasonbahl if you don't mind. I've never seen this bug before!

[JerresonJ]

This may be similar or the same issue we are facing right now. I haven't looked at the code any further to investigate but Faust is clearly overwriting the URI in our situation too.

When querying custom taxonomies the URI is overwritten via Faust to be an absolute URL as opposed to relative. This is causing issues for us as well..

Please address the issue. thanks.

[jasonbahl]

closing in favor of: #1653