Google Calendar Toolkit contribution

[jorge-jrzz]

Hello there!

I want to make a PR to this repository to add the Toolkit for interaction with Google Calendar, my main inspiration from the source code is the Gmail Toolkit, but I have some doubts about how to meet the requirements of the PR template and the different guides, I hope you can help me to make the PR push as soon as possible.

According to the README, as it's a functionality that makes API calls you have to do the integration tests, but there are no integration tests for the Gmail Toolkit with which I can guide me, because unlike other GPC tools, in these services, you don't have access with a simple API key.

integration_tests/
├── __init__.py
├── fake.py
├── feature_store
│   ├── test_feature_store_bq_vectorstore.py
│   └── test_feature_store_fs_vectorstore.py
├── terraform
│   └── main.tf
├── test_bigquery.py
├── test_bigquery_vector_search.py
├── test_check_grounding.py
├── test_docai.py
├── test_docai_warehoure_retriever.py
├── test_googlesearch_api.py
├── test_placeholder.py
├── test_rank.py
├── test_vertex_ai_search.py
└── test_vision.py

Another question about this PR that I have doubts about is related to the development experience, the idea is that the Calendar Toolkit can be installed in a similar way as the Gmail Toolkit is installed:

pip install -qU langchain-google-community\[calendar\]

To achieve this, the following would need to be added to langchain-google/libs/community/pyproject.toml:

calendar = ["google-auth-httplib2", "google-auth-oauthlib"]

Can I propose this in the PR? Why does the README mention that to add a dependency I have to do it with the extended_testing_deps.txt file

1. Open extended_testing_deps.txt and add the dependency
2. Add a unit test that the very least attempts to import the new code. Ideally, the unit test makes use of lightweight fixtures to test the logic of the code.
3. Please use the @pytest.mark.requires(package_name) decorator for any unit tests that require the dependency.

But there isn't extended_testing_deps.txt file.

My last question is about the notebooks for new integrations that are mentioned in the
PR template:

• If adding a new integration:

1. Include a test for the integration (preferably unit tests that do not rely on network access)
2. Add an example notebook showing its use (place in the docs/docs/integrations directory)

But again this route does not exist.

Thanks devs, and I hope you can help me to make this contribution 🤩