Clarify when the import flow and Farcaster manifest are still needed#1248
Open
gizdusum wants to merge 1 commit intobase:masterfrom
Open
Clarify when the import flow and Farcaster manifest are still needed#1248gizdusum wants to merge 1 commit intobase:masterfrom
gizdusum wants to merge 1 commit intobase:masterfrom
Conversation
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.
This adds a small clarification to the mini app docs for developers who are unsure whether they should follow the standard web app path or the older manifest/import flow.
The main issue is that it is easy to read the docs as saying both of these things at once:
/.well-known/farcaster.jsonand go through the import flowThis PR adds a short note to both quickstart pages so it's easier to choose the right path.
Closes #1247