Follow-up from "fix: respect duoFeaturesEnabled setting for Duo Chat actions"
The following discussion from !1601 (merged) should be addressed:
-
@erran started a discussion: (+1 comment) suggestion(non-blocking): How about building in support for caller specified
resourceId
now? It'd save confusion from someone expectingsendAiAction('xxx', { resourceId: 'gid://something/else' })
not respecting the specifiedresourceId
.const resourceId = variables.resourceId || await this.#manager.getProjectGqlId() || null; const request: GraphQLRequest<AiActionResponseType> = { type: 'graphql', query: actionQuery, variables: { ...variables, resourceId,
It'd require an additional test case.