feat(AppSync): Add JS resolver helper & matchers #79
Conversation
| } | ||
| } | ||
| `); | ||
| ``` |
There was a problem hiding this comment.
FYI, I removed support for string predicates.
in AppSync, it should always be a JSON anyway.
if the evaluated mapping template is not a valid js, it will throw an error.
doc/matchers/appsync.md
Outdated
|
|
||
| ### `appSyncResolver(input: AppSyncResolverInput)` | ||
|
|
||
| - `code`: A string with the `APPSYNC_JS`` resolver code |
There was a problem hiding this comment.
@bayoudhi I am considering changing this to be the path of a file, both in JS and mapping templates (VTL).
I don't think that inline code is useful. Especially in this context.
The code will always live somewhere else
There was a problem hiding this comment.
The question/issue would be to what directory the path should be relative to and how to handle that inside sls-jest.
There was a problem hiding this comment.
In the end this is what I did
bboure
changed the title
bboure
changed the title
bboure
changed the title
|
🎉 This PR is included in version 1.0.0-alpha.9 🎉 The release is available on: Your semantic-release bot 📦🚀 |
No description provided.