You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have a GraphQL schema with a query. The query uses a lambda resolver that connects to a REST API and fetches the data. I want to have the field TimeSchedules on the type AccessGroup to use a different resolver and I've managed to get this to work in the console but it doesn't seem to be possible with SAM.
On the REST Api access groups have time schedules but they're two different calls, and as I don't always need the latter, I think it's better to have it like this.
Hi @roger-zhangg ! The id is the Id of the access group. But as each access group might have a time schedule, it would be nice to request the time schedule along with the access group whenever I like that.
In the console it is easy to attach a resolver to a field
I have a GraphQL schema with a query. The query uses a lambda resolver that connects to a REST API and fetches the data. I want to have the field
TimeSchedules
on the typeAccessGroup
to use a different resolver and I've managed to get this to work in the console but it doesn't seem to be possible with SAM.Parts of schema:
On the REST Api access groups have time schedules but they're two different calls, and as I don't always need the latter, I think it's better to have it like this.
In SAM, I've tried this:
But then I get an error saying
This is quite easy in the Console where I can just attach a resolver to the spesific field itself.
Any suggestions?
The text was updated successfully, but these errors were encountered: