Revert "feat: Integrating thirdy party Slack API "

[jiashenC]

No description provided.

[jiashenC]

Is the previous PR #967 in a ready state? @kaushikravichandran

[kaushikravichandran]

Hi @jiashenC . The previous PR does not affect any component. I merged it because Aryan has to build on those changes. He had taken a look at the PR.

[jiashenC]

Hi @jiashenC . The previous PR does not affect any component. I merged it because Aryan has to build on those changes. He had taken a look at the PR.

I think it would be better that you merge this into Aryan's branch first and then merge everything together into staging. What do you think @xzdandy?

In addition, there are several things that can be improved for this PR

1. We'd like to add unit tests for each third-party handler.
2. Please remove slack_sdk from setup.py. Instead, it can be installed based on the handler by adding a requirements.txt. Here is the reference https://github.com/georgia-tech-db/evadb/tree/staging/evadb/third_party/databases/postgres.

[xzdandy]

Hi @jiashenC . The previous PR does not affect any component. I merged it because Aryan has to build on those changes. He had taken a look at the PR.

I think it would be better that you merge this into Aryan's branch first and then merge everything together into staging. What do you think @xzdandy?

In addition, there are several things that can be improved for this PR

1. We'd like to add unit tests for each third-party handler.
2. Please remove slack_sdk from setup.py. Instead, it can be installed based on the handler by adding a requirements.txt. Here is the reference https://github.com/georgia-tech-db/evadb/tree/staging/evadb/third_party/databases/postgres.

Yes I agree. Let's only merge the fully ready PR to staging.