Description

Currently, when the ripcord field is absent in the response, this does not cause an error even when the ripcord path is configured in the params.

The ripcord path is optional so when it's configured, it should be interpreted as expected in the response.

Changes

1. Don't skip ripcord check if ripcord is absent in the response but present in the params.

Steps to Test

1. yarn test packages/sources/generic-api
2. I tested it with all 18 existing feeds and streams that use generic-api with ripcord.

Quality Assurance

• If a new adapter was made, or an existing one was modified so that its environment variables have changed, update the relevant infra-k8s configuration file.
• If a new adapter was made, or an existing one was modified so that its environment variables have changed, update the relevant adapter-secrets configuration file.
• If a new adapter was made, or a new endpoint was added, update the test-payload.json file with relevant requests.
• The branch naming follows git flow (feature/x, chore/x, release/x, hotfix/x, fix/x) or is created from Jira.
• This is related to a maximum of one Jira story or GitHub issue.
• Types are safe (avoid TypeScript/TSLint features like any and disable, instead use more specific types).
• All code changes have 100% unit and integration test coverage. If testing is not applicable or too difficult to justify doing, the reasoning should be documented explicitly in the PR.