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

Updated tap-calendly as per the latest api reference #1

Open
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

shreejeet-atidiv
Copy link

  • new fields in streams.py as per latest calendly api reference. For each stream mentioned in streams.py, there were certain fields like invitees_counter, cancellation in events stream, which were mentioned in the latest api reference. These fields have been added.
  • made changes to setup.py. Setup.py did not have entry_points, classifiers, and modules mentioned. Added that.
  • Made changes to get_next_page_token in client.py, where it takes the next_page_token directly from the json response, instead of parsing the next page url for next_page_token -Made changes to config.sample.json, where start_date's format has been changed as per the api reference.

Description of change

(write a short description or paste a link to JIRA)

Manual QA steps

Risks

Rollback steps

  • revert this branch

- new fields in streams.py as per latest calendly api reference.
For each stream mentioned in streams.py, there were certain fields like invitees_counter, cancellation in events stream, which were mentioned in the latest api reference. These fields have been added.
- made changes to setup.py. Setup.py did not have entry_points, classifiers, and modules mentioned. Added that.
- Made changes to get_next_page_token in client.py, where it takes the next_page_token directly from the json response, instead of parsing the next page url for next_page_token
-Made changes to config.sample.json, where start_date's format has been changed as per the api reference.
@singer-bot
Copy link

Hi @shreejeet-atidiv, thanks for your contribution!

In order for us to evaluate and accept your PR, we ask that you sign a contribution license agreement. It's all electronic and will take just minutes.

@singer-bot
Copy link

You did it @shreejeet-atidiv!

Thank you for signing the Singer Contribution License Agreement.

Copy link

@shreejeetsahayold shreejeetsahayold left a comment

Choose a reason for hiding this comment

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

there have been api changes, which have been incorporated here.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants