Meta Issue: framegear

[cnasc]

Describe the solution you'd like

At some point it would be nice to group these into a project, but for the time being listing some outstanding ideas:

• show frame payload HTML tags (and copy button)
• show frame payload as an onchainkit metadata object (and copy button)
• verification
  • show required tags even when not present in payload (feat: always show required tag status #176)
  • show all possible tags (possibly collapsed) even if not present in payload
• distinct button icons for distinct button actions (e.g., post_redirect, mint, and link buttons) (tweak: button icons (framegear) #203)
• rendered frame should support all button actions
  • post
  • post_redirect
  • link
  • mint
• rendered frame should include text input in mock request (feat: pass input text through post action #201)
• allow user to select certain simulated conditions (e.g., liked/recasted, followed, etc.)
• favicon (awaiting design) (feat: add favicon (framegear) #204)
• Identify when a frame can accept debug actions, inform user what is possible
• more comprehensive light/dark mode styling (see feat: framegear add styles for light mode, make legible  #190)
• support fc:frame:state tag (see re: #185: Styling changes #193 (comment)) (feat: Frame now uses FrameMetadata instead of string record #232)
• frame input bug (state seems to persist after next frame renders)
• more sophisticated state handling (page through previous, time travel debugger)

Describe alternatives you've considered.

No response

[taycaldwell]

PR: #200

Rendered frame should support all button actions
Distinct button icons for distinct button actions

• post_redirect
• link

[cnasc]

@huntertdiamond I see you added a commit to add simulated conditions to the frame. Do you want to drive on that one? And/or cool if I build on it sometime in the next few days?