Query items with PK and response in an order based on range key

query-sort-by-rangekey.vtl

{
    "version" : "2017-02-28",
    "operation" : "Query",
    "query" : {
        "expression" : "author = :author",
        "expressionValues" : {
        	":author" : $util.dynamodb.toDynamoDBJson($ctx.args.author)
        }
    },
    ## false -> DESC ORDER
    "scanIndexForward" : false
}

@ohsik

1. Defining a key is a way to enable your data access pattern.
2. Using custom resolver is a way to control over Amplify. We know that Amplify has GraphQL Transform which will automatically create DynamoDB table and some default CRUD queries and mutations. But sometimes those autogenerated queries and mutations doesn't match our need or requirement. This is when custom field and resolver come in.

@koingdev Thank you! didn't know u replied here till today haha.

So as long as I have the scalable database structure, I can user resolvers for custom queries and mutations.

I ended up modifying the schema file little bit the way I think it makes sense here(https://gist.github.com/ohsik/1506c0530a6744cff158f8af408be731) and moving on to building the app again.

Thank you for the help again!