-
Notifications
You must be signed in to change notification settings - Fork 6
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
feat(preview): adding standardized preview data cards #697
Conversation
@@ -0,0 +1,556 @@ | |||
extend schema |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I had to add a seperate schema for admin because federation gets mad since our admin api does not implement some of the shared objects
3ee6ed3
to
9b6a97f
Compare
schema: | ||
subgraph_url: https://list-api.readitlater.com | ||
parser: | ||
#routing_url: https://parser-graphql-wrapper.readitlater.com |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
reason this one is commented out?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Was running it locally against my local parser
collection: | ||
routing_url: https://collection-api.readitlater.com | ||
# schema: | ||
# subgraph_url: https://collection-api.readitlater.com |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
are these below commented out due to no introspection?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
yeppp
Suspect IssuesThis pull request was deployed and Sentry observed the following issues:
Did you find this useful? React with a 👍 or 👎 |
Goal
Standardize all display logic across Pocket using the Preview Entity.
Requires: Pocket/content-monorepo#210
Implementation Details
I chose to specifically use GraphQL to do our intersystem communication so that we could focus on merging logic. For now this works pretty well and the router handles all flattening in our resolvers
https://mozilla-hub.atlassian.net/browse/POCKET-10474