How to access nested navigationItemUrl text property in Sanity query map?

7 replies
Last updated: Dec 9, 2022
I have a query returning:

0:{…} 8 properties
_createdAt:2022-12-07T23:19:09Z
_id:navigation
_rev:Bp455s9rtQ49wRO6vY4ZPz
_type:navigation
_updatedAt:2022-12-08T21:58:33Z
items:[…] 1 item
0:{…} 4 properties
_key:7f41faf793a8
_type:navigationItem
navigationItemUrl:{…} 2 properties
_type:link
internalLink:{…} 2 properties
text:login
navId:{…} 2 properties
_type:slug
current:mainMenu
title:Browse
I'm able to display the title "Browse" with


{navs.map((navs: any) => (
        <div key={navs._id}>{navs.title}</div>
      ))}
But I want to use navigationItemUrl's "text" in a map to output link urls.

How might I go about this?
AI Update

This is a JavaScript/TypeScript data traversal question rather than a Sanity-specific issue. Looking at your data structure, you need to access nested properties within the items array.

Based on your data structure, navigationItemUrl.internalLink contains the text property you want. Here's how to access it:

{navs.map((nav: any) => (
  <div key={nav._id}>
    <h3>{nav.title}</h3>
    {nav.items?.map((item: any) => (
      <div key={item._key}>
        {item.navigationItemUrl?.internalLink?.text}
      </div>
    ))}
  </div>
))}

The key points:

  • You need to map over nav.items (the array of navigation items)
  • Each item has a navigationItemUrl object
  • Inside that is internalLink which contains your text property
  • Use optional chaining (?.) to safely access nested properties
  • Use item._key as the key since each navigation item has that unique identifier

If you want to create actual links, you might do something like:

{navs.map((nav: any) => (
  <nav key={nav._id}>
    <h3>{nav.title}</h3>
    <ul>
      {nav.items?.map((item: any) => (
        <li key={item._key}>
          <a href={item.navigationItemUrl?.internalLink?.text}>
            {item.text || item.navigationItemUrl?.internalLink?.text}
          </a>
        </li>
      ))}
    </ul>
  </nav>
))}

TypeScript tip: Instead of using any, consider using Sanity TypeGen to generate proper types for your schema. This would give you autocomplete and type safety for these nested structures, making it much easier to work with complex data like this navigation structure.

Show original thread
7 replies
Ok, update!
I have gotten the "text" ("login") to show up in the link this way:

{navs.map((navs: any) =&gt; (
&lt;div key={navs._id}&gt;
&lt;a href={
/${navs.items[0].text}
}&gt;TEXT&lt;/a&gt; &lt;/div&gt;
))}

But I've added another item:


0:{…} 8 properties
_createdAt:2022-12-07T23:19:09Z
_id:navigation
_rev:cwf6PSmkIH3MXtFHyvxJDS
_type:navigation
_updatedAt:2022-12-09T00:18:00Z
items:[…] 2 items
0:{…} 4 properties
_key:7f41faf793a8
_type:navigationItem
navigationItemUrl:{…} 2 properties
_type:link
internalLink:{…} 2 properties
_ref:783ff653-fa25-4caa-ad69-dcf78dcaa970
_type:reference
text:login
1:{…} 4 properties
_key:85a628a4890b
_type:navigationItem
navigationItemUrl:{…} 2 properties
_type:link
internalLink:{…} 2 properties
_ref:b4d875e5-798e-401f-ac30-8b4ad96ecb82
_type:reference
text:blog
navId:{…} 2 properties
_type:slug
current:mainMenu
title:Browse
And I want to have the map output them both... What do I do?
You’ll want to map over that
items
array. I may have made up a
_key
value that’s not in your content, but perhaps something like:
{navs.map((nav) => (
  <div key={nav._id}>
    {nav.items.map((item) => (
      <a key={item._key} href={`/${item.text}`}>TEXT</a>
    ))}
  </div>
))}
user A
Ok, let me try that - I'll get back to you
user A
It works! YOU'RE BRILLIANT!!!!
Side note... so many maps... Is this normal?
Yes, if you have an array nested in an array, you’ll need to map over both. Depending on your setup you may want to add some guards (for example, what happens if
items
is empty? What if
navs
is empty?), but otherwise this should be fine and is completely typical.
user A
Brilliant, thank you!

Sanity – Build the way you think, not the way your CMS thinks

Sanity is the developer-first content operating system that gives you complete control. Schema-as-code, GROQ queries, and real-time APIs mean no more workarounds or waiting for deployments. Free to start, scale as you grow.

Was this answer helpful?