-
Notifications
You must be signed in to change notification settings - Fork 184
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
Resolver Mappings #25
Comments
perfect! If you want we can hop on skype or something today and I can give you a rundown of the process using example in https://github.com/serverless/serverless-graphql with deployment steps. Also, curious if you already have access to appsync? Also, yes IMO serverless yml should drive the mappings and we should also give the location of the mapping templates in the directory. |
Awesome, there's something for initial review up now in #27 I do have AppSync access, I'm going to keep trying to get more going this weekend, like maybe the elastic search stuff, so if we get a chance to hop on a call or IM or chat over issues today/next week that would be great! |
sounds good |
@jpstrikesback thanks for fixing this! |
Cheers! |
Just a quick note to say I'm going to be working on making the resolver mappings a bit more generalized.
Am I right to think that the serverless.yml should drive the resolver mappings? i.e.:
The text was updated successfully, but these errors were encountered: