# Ts issue with contentrelationship fields

**URL:** <https://community.prismic.io/t/ts-issue-with-contentrelationship-fields/18035>\
**Category:** Developing with Prismic\
**Tags:** typescript, nuxtjs\
**Created:** [November 20, 2024, 2:22pm UTC](https://community.prismic.io/t/ts-issue-with-contentrelationship-fields/18035 "2024-11-20T14:22:36Z")\
**Posts on this page:** 1\
**Showing post:** 3

<div class="post-metadata">

**Author:** ![Phil](https://dub1.discourse-cdn.com/flex013/user_avatar/community.prismic.io/phil/32/14_2.png) [@Phil](https://community.prismic.io/u/Phil)\
**Post date:** [November 21, 2024, 11:01am UTC](https://community.prismic.io/t/ts-issue-with-contentrelationship-fields/18035/3 "2024-11-21T11:01:12Z")

</div>

Hi @jankohlbach,

We've discussed this previously here and you'll find the solution in that thread 🙂

> [@TypeScript Content Relationships in Nuxt](https://community.prismic.io/t/typescript-content-relationships-in-nuxt/14700/12):
>
> Hey @leopold, Thanks for your patience! I looked into this and I think I might have a solution for you. This is based on a solution that our engineer Angelo developed for typing fetchLinks in Next.js, but I've tested it in Nuxt and it seems to be working. Typically we use the $prismic.isFilled helpers to check if a property exists. However — as you have encountered here — TypeScript doesn't know the structure of the linked data. Angelo wrote a helper to take care of that — isFilledRelatedData(…

Thanks.

---

_[View the full topic](https://community.prismic.io/t/ts-issue-with-contentrelationship-fields/18035)._