Migrate frontpage post to be lexicon first #199
Draft
Conversation
This file contains 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
|
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
tom-sherman
commented
Nov 6, 2024
Comment on lines
+151
to
+153
| await atproto.fyi.unravel.frontpage.post.delete({ | ||
| rkey, | ||
| }); |
There was a problem hiding this comment.
This is essentialy untyped because of a bug in the lex-cli generated code. See bluesky-social/atproto#2952
I'll probably leave this in draft until a solution is found for that.
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 is the first PR in a series to migrate us to be "lexicon-first". In that we define our types in atproto lexicon DSL and then generate the types, schemas, and API clients from that.
I'm going type-by-type with the end goal of basically removing all of our frontpage-specific code in the
lib/data/atprotofolder.