Scott Rippee

Ability to target a specific channel using gstart

1

Currently using `!gcreate` to start giveaways in channels other than where the command is issued, but would be nice to be able to use `!gstart`.

# Description The documentation shows this for accessing the output variables from a different component in the same org: ``` ${output:[app]:[stage]:[instance name].[output]} ``` With example input like: ``` inputs: roleArn:...

I have an issue where I not able to detect that a query failed with a response code of 404: ``` stores.then(function(records) { Em.Logger.log("In stores then"); Em.Logger.log(records); records.reload().then(function(records2) { Em.Logger.log("In...

@hypexr Removed memoizeWith from getAccountId so the incorrect account id will not be returned when deploying from one provider to the next

1

To resolve https://github.com/serverless-components/graphql/issues/23

Incorrect account ids in lambda policy

2

graphql 3.0.3 I have graphql components configured to deploy to different stages each with a different provider defined in the serverless web ui with each provider being a different aws...

Redeploying an appsync API disconnects any existing connected resolvers

2

When an appsync api is deployed and then extended with additional graphql components that reference it's `appId` the resolvers they attached are disconnected. To fix each component that references the...

Shouldn't require/execute resolvers.js when deploying the built in resolvers lambda

4

Unexpected errors can occur when resolvers.js is loaded as part of the deploy process. For example, it's common to create things like DB connections outside of the handler so that...

It doesn't look like there's support for HTTP resolvers. When I specify an endpoint it assumes it's the elasticsearch resolver. Are there plans to add it?