rich text support and test output#1
Open
gnikxela0328 wants to merge 1 commit intobluesky-social:mainfrom
Open
Conversation
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
1 participant
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.
Attempted to make a test post at ATmosphere Vancouver and could not tag @alex.bsky.team using plain text input. PR introduces rich text support from npm docs.
https://www.npmjs.com/package/@atproto/api
There is no atomic example of implementing rich text posting. I started at the "Rich Text" section on the docs, then had to search for the "AtpAgent" implementation. It was not clear why the usage of a custom fetch was required in order to leverage rich text. Naively copying the code into the exercise worked, but this was an educated guess.