Fields are flagged as unused after .filter()

[mattias800]

When you have a component that takes a list, and you have logic that filters the list, the fields are incorrectly flagged as unused.

Here is a code example.

export interface CabinImageCarouselProps {
  images: Array<FragmentOf<typeof cabinImageCarouselCabinImageFragment>>;
}

export const cabinImageCarouselCabinImageFragment = graphql(`
  fragment CabinImageCarousel_CabinImage on CabinImage {
    altText
    imageDimensionCode
    url
  }
`);

export const CabinImageCarousel: React.FC<CabinImageCarouselProps> = (
  props
) => {
  const images = readFragment(
    cabinImageCarouselCabinImageFragment,
    props.images
  );

  const seatImages = useMemo<Array<CarouselImage>>(() => {
    return (
      images
        .filter((i) => i.imageDimensionCode === ImageDimensionCode["300x500"])
        .map((p) => ({
          url: p.url,
          alt: p.altText,
        })) ?? []
    );
  }, [images]);

  return <ImageCarousel images={seatImages} />;
};

In this case, altText and url are flagged as unused.

If I remove the filter, they are no longer flagged as unused.

Reproduction

No response

gql.tada version

gql.tada v1.8.6

Validations

• I can confirm that this is a bug report, and not a feature request, RFC, question, or discussion, for which GitHub Discussions should be used
• Read the docs.
• Follow our Code of Conduct

[JoviDeCroock]

I am assuming we are missing a case for chained methods over here as it correctly picks up the accessor from filter but not from map