Feat: Better Handling of FrameButton post actions

[brendan-defi]

What changed? Why?

• updated FrameButtonMetadata to allow custom postUrl property
• updated getFrameMetadata to handle custom postUrls on Frame Buttons

Notes to reviewers

How has it been tested?

[vercel]

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name	Status	Preview	Comments	Updated (UTC)
onchainkit-coverage	❌ Failed (Inspect)			Aug 15, 2024 10:26pm
onchainkit-playground	❌ Failed (Inspect)			Aug 15, 2024 10:26pm

[Zizzamia]

Is this part of the Frame Spec? And where is this writtend?

[brendan-defi]

Per Button Actions, we are told that a post should send an HTTP request to the button's post_url.

But as currently configured, getFrameMetadata does not set a fc:frame:button:[id]:post_url property for post actions, only tx actions:

  if (buttons) {
    buttons.forEach((button, index) => {
      metadata[`fc:frame:button:${index + 1}`] = button.label;
      if (button.action) {
        metadata[`fc:frame:button:${index + 1}:action`] = button.action;
      }
      if (button.target) {
        metadata[`fc:frame:button:${index + 1}:target`] = button.target;
      }
      if (button.action && button.action === 'tx' && button.postUrl) {
        metadata[`fc:frame:button:${index + 1}:post_url`] = button.postUrl;
      }
    });
  }

The above change to FrameButtonMetadata is required for strict type-checking of the getFrameMetadata logic.

[vercel]

@brendan-defi is attempting to deploy a commit to the Coinbase Team on Vercel.

A member of the Team first needs to authorize it.