Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add custom function support #1021

Open
wants to merge 13 commits into
base: main
Choose a base branch
from
Open

Add custom function support #1021

wants to merge 13 commits into from

Conversation

WilliamBergamin
Copy link
Contributor

This PR includes all the changes from #986 aims to add support for custom functions in Bolt Python

Feedback

I'm looking for feedback on

  • Usability, is this what we envisioned the developer experience would be?
  • Does this aline with the Bolt-js experience?
  • Implementation, does this implementation align with bolt principles
  • Tests, is this missing tests that could be valuable for the feature

Testing

This gist was created to show how to test these new feature, use it with the following steps

  1. Create a new app
    a. Head to https://api.slack.com/apps/?new_app=1
    b. Click "From an app manifest"
    c. Select YAML and paste the above manifest.yml content
    d. Click create button
  2. Install the app into org/workspace
    a. Install the app anyways (when the workspace is in an Org, org-wide installation is required to publish functions)
    b. Grab the xoxb- token (Settings > Install App > Bot User OAuth Token)
    c. export SLACK_BOT_TOKEN=xoxb-...
  3. Set up Socket Mode
    a. Head to Settings > Basic Information > App-Level Tokens on the https://api.slack.com/apps page
    b. Generate a new token with connections:write scope
    c. export SLACK_APP_TOKEN=xapp-...
  4. Spin up the app
    a. Add app.py and async_app.py with the above source code
    b. Pull the latest PR branch of bolt python to your local
    c. Run scripts/build_pypi_package.sh this will generate a .whl in the dist/ folder
    d. (Optional) In your project set up a venv with python -m venv .venv and source .venv/bin/activate
    e. pip install global/path/to/bolt-python/dist/something.whl
    f. pip install aiohttp
    g python app.py or python async_app.py
  5. Add the custom step to a workflow
    a. Open the workflow builder
    b. Create a new workflow with a link trigger
    d. Seach "Hello" in the Steps view on the right side
    e. Add the step to the workflow (you can set any user ID as the input)
    f. Publish the workflow

Category

  • slack_bolt.App and/or its core components
  • slack_bolt.async_app.AsyncApp and/or its core components
  • Adapters in slack_bolt.adapter
  • Document pages under /docs
  • Others

Requirements

Please read the Contributing guidelines and Code of Conduct before creating this issue or pull request. By submitting, you are agreeing to those rules.

  • I've read and understood the Contributing Guidelines and have done my best effort to follow them.
  • I've read and agree to the Code of Conduct.
  • I've run ./scripts/install_all_and_run_tests.sh after making the changes.

* add listener

---------

Co-authored-by: Kazuhiro Sera <seratch@gmail.com>
Copy link

codecov bot commented Jan 25, 2024

Codecov Report

Attention: Patch coverage is 98.50000% with 3 lines in your changes are missing coverage. Please review.

Project coverage is 91.96%. Comparing base (dbe2333) to head (9b94f8f).

Files Patch % Lines
slack_bolt/request/internals.py 93.10% 2 Missing ⚠️
slack_bolt/context/base_context.py 90.00% 1 Missing ⚠️
Additional details and impacted files
@@            Coverage Diff             @@
##             main    #1021      +/-   ##
==========================================
+ Coverage   91.76%   91.96%   +0.20%     
==========================================
  Files         181      190       +9     
  Lines        6315     6512     +197     
==========================================
+ Hits         5795     5989     +194     
- Misses        520      523       +3     

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

Copy link
Member

@seratch seratch left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Left a few comments

slack_bolt/app/app.py Outdated Show resolved Hide resolved
slack_bolt/app/app.py Outdated Show resolved Hide resolved
slack_bolt/app/async_app.py Outdated Show resolved Hide resolved
self.client = client
self.function_execution_id = function_execution_id

def __call__(self, outputs: Dict[str, Any] = {}) -> SlackResponse:
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

If you need a default value here, you should not use an empty dict value for argument default. See https://stackoverflow.com/questions/26320899/why-is-the-empty-dictionary-a-dangerous-default-value-in-python for more details

Suggested change
def __call__(self, outputs: Dict[str, Any] = {}) -> SlackResponse:
def __call__(self, outputs: Optional[Dict[str, Any]] = None) -> SlackResponse:

And the following lines of code should be updated accordingly.

If the default value is not necessary, you can simply remove it.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Wow TIL, did not think the default value would be assigned to the function itself 😮

self.client = client
self.function_execution_id = function_execution_id

async def __call__(self, error: str = "") -> AsyncSlackResponse:
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Do we want to allow no error here? I believe we don't need to have the default value here.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I agree we don't need the default value here 👍

@WilliamBergamin WilliamBergamin marked this pull request as ready for review May 14, 2024 13:52
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants