frames-v2

Developer ecosystem @farcaster, co-founder @bountycaster. Previously: co-founder of Scalar Capital, product at Coinbase, co-producer @ethereumfilm

Building @warpcast and @farcaster / dad / like to read, cook, ski, code

has anyone else encountered frame.sdk.context.user changing payload data? it used to return { fid, username } it now seems to be returning an object which inside of it has a user object which inside of it has { fid, username } // cc @linda @deodad

aspiring person // DC me if you need help making frames

possible we unintentionally broke this, will look

I'm eth newbie..just learning
(working on @farcaster)

terminally.online

Farcaster Development Boutique @ https://dTech.vision 💜 in love with tech 🤓decentralization, fitness and oldschool rap 😎

Not aware of any change there personally. 

export type FrameContext = {
  user: {
    fid: number;
    username?: string;
    displayName?: string;
    pfpUrl?: string;
  };
  location?: FrameLocationContext;
  client: {
    clientFid: number;
    added: boolean;
    safeAreaInsets?: SafeAreaInsets;
    notificationDetails?: FrameNotificationDetails;
  };
};

Is what it should return according to the FIP

Not aware of any change there personally. 

export type FrameContext = {
  user: {
    fid: number;
    username?: string;
    displayName?: string;
    pfpUrl?: string;
  };
  location?: FrameLocationContext;
  client: {
    clientFid: number;
    added: boolean;
    safeAreaInsets?: SafeAreaInsets;
    notificationDetails?: FrameNotificationDetails;
  };
};

Is what it should return according to the FIP

https://github.com/farcasterxyz/protocol/discussions/205

Yes! i changed to something like this and fixed.

const context = await frame.sdk.context;
const user = context?.user;
console.log("User context received:", user);