sync all forms when config not provided

[aaronbannin]

Description of change

If no form IDs provided in config, sync all forms.

Currently, the tap only syncs data for forms that are explicitly declared within the config. This is fine for accounts with a low number of forms; but is unable to pull data automatically from an active Typeform account.

If the forms config value is null or '', sync data for all known forms.

Improves stability in two ways:

• Forms can be deleted in Typeform; causing the tap to fail and requiring settings to be manually updated. If you sync all forms, then the tap will only attempt forms that exist within the API.
• A form without quesitons currently causes a fatal error. This PR treats nested streams as optional.

This change is backwards compatible.

• If an existing deployment has forms defined within config, there is no change.
• If an existing deployment has a form ID defined within the config that is no in their Typeform account, there is no change.
• An existing deployment will only see a change if the config.forms value is set to null or ''

Manual QA steps

Tested against live Typeform account.

• In config.json; forms: null
• In config.json; forms:""
• In config.json; forms:"validFormId"

Risks

• What value does Stitch UI fill in if the test box is empty?
• This can increase volume for large Typeform deployments

Rollback steps

• revert this branch

[singer-bot]

Hi @aaronbannin, 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]

You did it @aaronbannin!

Thank you for signing the Singer Contribution License Agreement.

[kethan1122]

Hello @aaronbannin. we are about to review this PR, any reason for closing this PR

[aaronbannin]

Sorry; I disconnected the upstream fork and didn't realize that it would close the PR. What would be the best way to proceed, I can try to create a new fork? Or someone else could create a new PR with these changes?

[kethan1122]

No worries, We have created a new PR based on your changes. Please, have a look at this PR in-case we missed something.