docs: clarify when Farcaster manifest is required for Mini Apps#1257
Open
Kubudak90 wants to merge 1 commit intobase:masterfrom
Open
docs: clarify when Farcaster manifest is required for Mini Apps#1257Kubudak90 wants to merge 1 commit intobase:masterfrom
Kubudak90 wants to merge 1 commit intobase:masterfrom
Conversation
Add 'Which flow should I use?' section to help developers understand: - When Farcaster manifest is required vs optional - Decision tree for choosing migration paths - Clear distinction between Base App-only and Farcaster-integrated apps Fixes base#1247
Collaborator
🟡 Heimdall Review Status
|
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Problem
The Mini Apps documentation doesn't clearly distinguish between two different scenarios:
Solution
Added a clear note box explaining when Farcaster manifest is required vs not required.
Checklist