support Data Access API#1439
Conversation
- added https://api.slack.com/methods/assistant.search.context api - added `assistant_thread` attribute to Event API `message`, `app_mention` envets https://api.slack.com/docs/apps/data-access-api#event-listener
|
@nktks I'm not going to review this until you move it into ready for review - just wanted to call that out explicitly. Thanks for adding this. |
|
@nktks just checking in on this - no pressure at all but want to make sure you didn't just leave it at Draft by mistake 🙏 |
|
@nlopes Sorry for the confusion. |
|
Realised that developer sandbox environments don't have this enabled :( |
|
Yes. |
|
@nlopes Hello. So I changed as ready for review this PR. |
|
|
||
| // Handle a specific event from EventsAPI | ||
| socketmodeHandler.HandleEvents(slackevents.AppMention, middlewareAppMentionEvent) | ||
| socketmodeHandler.HandleEvents(slackevents.Message, middlewareMessageEvent) |
There was a problem hiding this comment.
I would prefer if this was an example on its own. That's to make sure that people that don't have this API yet, won't be affected if they want to run this example (basically it will save me answering queries about why this example might not be working).
This reverts commit aa7a868.
assistant_threadattribute to Event APImessage,app_mentionenvets https://api.slack.com/docs/apps/data-access-api#event-listenerAgent & AI Appsenabled app.Pull Request Guidelines
These are recommendations for pull requests.
They are strictly guidelines to help manage expectations.
PR preparation
Run
make pr-prepfrom the root of the repository to run formatting, linting and tests.Should this be an issue instead
API changes
Since API changes have to be maintained they undergo a more detailed review and are more likely to require changes.
Examples of API changes that do not meet guidelines: