Repository navigation
[6.x] Link Fieldtype API changes - #11375
Merged
Merged
Conversation
duncanmcclean
changed the title
jasonvarga
requested changes
Oct 16, 2025
jasonvarga
left a comment
jasonvarga
left a comment
Member
There was a problem hiding this comment.
It's outputting too much. It should get shallow augmented the same way as you'd see if you used the entries fieldtype.
jasonvarga
changed the title
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Right now, the REST API returns the URLs of links configured using the Link fieldtype.
However, for entry links, there's no way to know any more information about the link, other than its URL. You could loop through and query each collection individually but that's certainly far from ideal.
In Antlers/Blade land, #8911 made it possible to get more "information" about a linked entry. However, that change was never reflected in the REST API, due to the fact it'd be a breaking change.
This PR follows-up and makes that breaking change so consumers of the REST API can get more context of linked entries without having to do a lot of work.