Extracting the final object from a nested array in JavaScript (AirTable Scripting)

Other Questions Airtable
1

I’m new to JavaScript and working on a project using the LegiScan API to update an AirTable. I can make API calls, but I’m stuck on getting vote information. My goal is to automatically pull the most recent vote for each bill, which is the last object in the ‘votes’ array.

Here’s what I’ve done so far:

let apiToken = 'my_api_token'
let table = base.getTable('Test Bills')
let { records } = await table.selectRecordsAsync()

for (let record of records) {
  let billUpdate = await remoteFetchAsync(`https://api.legiscan.com/?key=${apiToken}&op=getBill&id=${record.name}`)
  let data = await billUpdate.json()
  console.log(data.bill)

  // This part isn't working
  const lastVote = data(data.votes.length - 1)
}

I’m struggling with two things:

  1. How to correctly set the lastVote variable
  2. Is using length - 1 the best way to get the last object in an array?

When I try to run this, I get an error:

TypeError: Cannot read properties of undefined (reading 'length')

Any tips would be really helpful! I’m more familiar with R, so JavaScript is still new to me.

2

hey, i’ve dealt with similar stuff before. looks like ur data structure might be a bit different than u think. try this:

const lastVote = data.bill?.votes?.[data.bill.votes.length - 1] ?? null;

this uses optional chaining (?.) and nullish coalescing (??) to safely access the last vote. it’ll handle cases where votes might not exist without throwing errors. hope this helps!

3

As someone who’s worked extensively with APIs and JavaScript, I can shed some light on your issue. The error you’re seeing suggests that data.votes is undefined. This could happen if the API response doesn’t always include a ‘votes’ property.

To fix this, you should first check if the ‘votes’ property exists and is an array. Then, you can safely access the last element. Here’s how you could modify your code:

const votes = data.bill.votes;
const lastVote = votes && votes.length > 0 ? votes[votes.length - 1] : null;

This approach is safer and will prevent errors. As for your second question, using length - 1 is indeed a common way to access the last element of an array in JavaScript. However, newer versions of JavaScript offer a more elegant solution:

const lastVote = votes && votes.length > 0 ? votes.at(-1) : null;

The at() method allows you to use negative indices, making it easier to access elements from the end of the array. Just remember to check for the existence and non-emptiness of the array first to avoid potential errors.

4

I’ve encountered similar challenges when working with nested API responses. From what I can see, the issue lies in how you’re accessing the ‘votes’ array. The data structure might be different than you expect.

Try this approach:

const lastVote = data.bill && data.bill.votes && data.bill.votes.length > 0
  ? data.bill.votes[data.bill.votes.length - 1]
  : null;

This checks if ‘bill’ and ‘votes’ exist before attempting to access the last element. It’s a defensive coding practice that helps prevent those pesky ‘undefined’ errors.

As for getting the last element, your instinct with ‘length - 1’ is correct. It’s a reliable method, especially when working with APIs where you can’t always guarantee the availability of newer JavaScript features across different environments.

Remember to always validate API responses. They can change unexpectedly, and robust error handling will save you headaches down the line.