How are resolvers actually attached? Cannot see proper resolver.
See original GitHub issue** Which Category is your question related to? ** Generation of fields resolvers
** What AWS Services are you utilizing? ** AWS AppSync
** Provide additional details e.g. code snippets ** My local schema looks like this:
type BookEntity @model @searchable {
id: ID!
bookSection: String!
bookOrder: String!
bookCode: String!
bookCodeTitleRu: String!
bookElementOrder: String!
type: String!
content: AWSJSON!
notes: [Note] @connection(name: "BookEntityNotes")
bookmarks: [Bookmark] @connection(name: "BookEntityBookmarks")
highlights: [Highlight] @connection(name: "BookEntityHighlights")
}
type Note
@model
@auth(rules: [{allow: owner}])
{
id: ID!
content: String!
bookEntity: BookEntity! @connection(name: "BookEntityNotes")
}
type Bookmark
@model
@auth(rules: [{allow: owner}])
{
id: ID!
bookEntity: BookEntity! @connection(name: "BookEntityBookmarks")
}
type Highlight
@model
@auth(rules: [{allow: owner}])
{
id: ID!
bookEntity: BookEntity! @connection(name: "BookEntityHighlights")
}
After amplify push and placing items in BookEntity DynamoDB table I can successfully query BookEntities using following query:
export const listBookEntitys = `query ListBookEntitys(
$filter: ModelBookEntityFilterInput
$limit: Int
$nextToken: String
) {
listBookEntitys(filter: $filter, limit: $limit, nextToken: $nextToken) {
items {
id
bookSection
...
Now, I want to see how an actual resolver works for this query in AWS AppSync Console. So I go there…
In the console’s schema definition, I see:
listBookEntitys(filter: ModelBookEntityFilterInput, limit: Int, nextToken: String): ModelBookEntityConnection
ModelBookEntityConnection:
type ModelBookEntityConnection {
items: [BookEntity]
nextToken: String
}
I see that there is no resolver attached to items field or BookEntity one. What am I missing? How is this works on the front but do not have any resolvers on the back?
Issue Analytics
- State:
- Created 5 years ago
- Comments:7
Top Results From Across the Web
AppSync detached resolvers · Issue #146 - GitHub
It is possible for resolvers to become detached when an incorrect schema is deployed and correcting the schema does not reattach the ...
Read more >Test and debug resolvers (VTL) - AWS AppSync
AWS AppSync executes resolvers on a GraphQL field against a data source. As described in Resolver mapping template overview, resolvers communicate with data ......
Read more >Resolvers - an overview | ScienceDirect Topics
One possible solution is to couple two resolvers by using a gear system (see Fig. 4.15) so that the second resolver will rotate...
Read more >Angular routing resolver not resolving - Stack Overflow
Try using. take(1) or first. operator to mark the completion of Observable . The resolve waits for Observable to complete before continuing.
Read more >API (GraphQL) - Overwrite & customize resolvers - Amplify Docs
Let's say you have a simple schema.graphql... ... and you want to change the behavior of request mapping template for the Query.getTodo resolver...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found

I spent two hours trying to figure out why my “attach resolver” buttons weren’t showing up before finding this issue and scrolling right. I have a moderate resolution screen. Maybe this is a bug, just in the appsync UI?
@muhendzera @jkeys-ecg-nmsu I’m not sure who should be capturing this issue - but it’s a big deal.